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

Annotations already declare read-only, idempotent, non-destructive, and non-open-world behavior. The description adds useful context by naming the data source, mentioning live prices and intro deals, and saying results are links to newvsts.com, though it does not cover result ordering or rate limits.

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, front-loaded with the resource and scope, then the filters and return type. There is no filler or repetition, and every clause contributes useful context.

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?

For an 8-parameter search tool with no output schema, the description says it returns links but does not describe the result shape, fields, or ordering. Annotations cover safety details well, but sibling routing and return-value expectations remain thin.

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?

Schema description coverage is 88%, so most parameter meaning is already supplied by the schema. The description only summarizes filter categories that the schema already documents and does not add syntax, defaults, or other semantics beyond it.

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?

States a specific verb and resource: search NewVSTs' tracker of recently released audio plugins, including formats and price context. It is clear what the tool does, but it does not explicitly distinguish itself from siblings like get_new_releases or get_deals_ending_soon.

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 lists filter dimensions such as keyword, type, format, OS, and price, which implies filtered discovery usage. However, it gives no explicit when-to-use or when-not-to-use guidance, and does not route the agent away from overlapping siblings.

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