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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely useful behavioral context beyond them: small-sample suppression, that these are not execution/success counts, that vendor integrations are untested, and that CapaLens does not certify vendors. It does not describe the return structure in detail, keeping it from a 5.

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?

Front-loads the core purpose before piling on disclaimers, and the sentences are information-dense with little obvious filler. The trailing caveats are relevant but numerous, making it slightly heavy for a read tool.

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?

With no output schema and 33% schema coverage, the description should carry return-shape duty, yet it only hints at one field (vendorTestingPolicy) and otherwise describes caveats. It is adequate for interpreting the data's meaning but incomplete for an agent needing to know what the results contain.

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 coverage is only 33%, and the description partially compensates: 'optionally by software' maps to softwareId and 'for 1, 7 or 30 days' reinforces the days enum (already in schema). softwareId's lookup semantics and days' default are otherwise unexplained, so the compensation is incomplete.

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 concrete verb and resource: 'Read anonymous directory-query observations for 1, 7 or 30 days, optionally by software.' An agent can tell this is a usage-metrics read, not a review or ranking tool. It does not explicitly name or contrast with siblings like get_review_summary or compare_software, so it falls short of a 5.

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 implies context (read observations over a window, optionally scoped to software) and clarifies what the numbers are NOT ('not downstream execution or business-success counts'), which aids interpretation. But it never states when to reach for this tool versus compare_software or get_review_summary, so usage guidance remains implied rather than explicit.

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