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

No annotations exist, so description carries full burden. Discloses data volume (85k+ events), refresh frequency (twice-weekly to quarterly), pricing ($0.1/call), and pagination via cursor. Could mention idempotency or rate limits, but sufficient for a feed tool.

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?

Single dense paragraph, does not waste words. Front-loaded with main purpose, then lists event types, usage context, filters, data size, refresh, pricing. Every sentence provides value.

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?

Covers purpose, filters, data size, refresh, and pricing. However, missing description of output structure (fields per event) since no output schema exists. Slight gap for complex tool with 7 parameters.

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 57%, but description enriches parameters: lists event types with names, explains 'since' format, 'cursor' as keyset. Adds context for NPI and CCN parameters implicitly. Compensates for lower schema coverage.

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 specific verb+resource: 'Provider change-event feed over 7 federal sources'. Lists defined event types and explicitly answers a clear user question. Clearly distinguishes from sibling tools which focus on static searches.

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?

Clear context: 'Answers: what changed in my territory since I last looked?' and filter options provided. Does not explicitly state when not to use or name alternatives, but the use case is well-defined.

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