buygit_compare

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

Describes the tool as a single-call operation that returns specific fields and handles unknown slugs gracefully. With no annotations provided, the description carries the full burden and does so adequately, though it could be more explicit about any side effects or read-only nature.

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?

Two sentences, no wasted words. Front-loaded with purpose and key fields, followed by usage guidance and error behavior. Highly efficient.

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?

Given the tool has one parameter and an output schema, the description covers purpose, usage, error handling, and differentiation from alternatives. No gaps identified.

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?

The description adds context that slugs should come from prior tool results, which is not in the schema. Schema coverage is 0%, but the description compensates by providing usage context and the allowed range of 2-5 items.

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 description clearly states the tool's purpose: 'Single-call side-by-side of 2-5 listings' listing specific fields. It distinguishes from sibling tools by mentioning that equivalent workflows need multiple calls and lack license compatibility.

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?

Provides clear guidance to pass slugs from prior tool results and explains that unknown slugs return 'not found' entries instead of errors. However, it does not explicitly state when not to use the tool or list specific alternatives.

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