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

No annotations are provided, so the description carries full burden. It discloses that the data is 'snapshotted' (not real-time), but does not mention read-only nature, authentication needs, or side effects. Some behavioral context but limited.

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 a single, front-loaded sentence with key verbs and resource. It is efficient but could be slightly more structured by grouping filter types.

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 13 parameters and no output schema or annotations, the description is too brief. It does not explain return format, pagination (despite a limit parameter), or what 'enrichment' entails. More details are needed for a complex search 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?

Schema description coverage is 77% (high), so baseline is 3. The description adds high-level filter categories but does not compensate for the 3 undocumented parameters (keyword, maxAmount, minAmount). The schema already documents most parameters.

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 performs ad-hoc search/enrichment over snapshotted grants and trials, listing example filters (keyword, sponsorClass, topic, $ range). It distinguishes from siblings by specifying the scope and flexibility.

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 usage for ad-hoc searching but does not explicitly state when to use this tool versus alternatives like delta_digest or whats_changed_since. No exclusions or when-not guidance is provided.

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