buygit_diff_versions

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

With no annotations provided, the description fully discloses behavior: it returns snapshot-driven deltas when conditions are met, otherwise returns current state with a 'gated_on' hint. This informs the agent about the tool's limitations and expected outputs.

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 two concise sentences, front-loading the main purpose and then detailing the conditional behavior. No extraneous words; every sentence provides essential information.

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's complexity (parameter count 3, output schema present), the description covers all critical aspects: the diff operation, conditional behavior based on operator settings, and a hint mechanism. It fully equips an agent to decide when and how to invoke the tool.

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?

All three parameters are described in the input schema with 100% coverage. The description adds value by explaining that 'slug' comes from a prior tool call, 'from' is clamped to listing.created_at, and 'to' defaults to now, which goes beyond the schema's basic descriptions.

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 it performs a time-window diff for a BuyGit listing, checking changes in license, popularity, or risk between two dates. It explicitly claims to answer questions no other MCP can, distinguishing it from siblings.

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 explains when to use the tool (to detect regressions over time) and provides clear conditions (requires TRENDING_V2_ENABLED and snapshot table; otherwise returns current state with a hint). This gives an agent concrete guidance on prerequisites and fallback behavior.

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