Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds critical operational behaviors that are not covered by the annotations (e.g., it requires a 'signed HaggleBoard offer (format v0)' and the 'Ed25519 public key'). These requirements are specific to the technical behavior of the invocation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is detailed and necessary due to the complexity and specific technical requirements. While slightly longer than necessary, every sentence provides unique value (e.g., safety disclaimers, format versions).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description successfully defines the full context for the tool: it is a seller-side tool for agents, operating in a testing environment, utilizing specific cryptography (Ed25519), and adhering to format v0 standards.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Given the 0% schema description coverage, the description does an excellent job of explaining the semantics of the required parameters: 'message' must be a 'signed HaggleBoard offer (format v0)' and 'seller_public_key' must be an 'Ed25519 public key.'

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The title and description clearly state the purpose is to submit a HaggleBoard offer (make_offer). It specifies the operational context of being 'Seller side' and 'for testing your own seller agent,' immediately distinguishing it from other potential seller actions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit usage constraints, including warnings that the tool is 'Not affiliated with any store, brand or platform.' and detailing the specific scope ('You see the need through a disclosure filter'). This helps prevent agents from using it in real-world or unauthorized scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.