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

The description adds meaningful behavioral context beyond the annotations: it warns against constructing IDs (which implies failure modes for malformed IDs) and reveals that the tool does not count toward monthly search quota. Annotations already cover read-only, idempotent, and non-destructive traits, so this extra context is valuable.

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-loaded with the primary purpose, followed by a salient usage warning. No wasted words.

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 a single-parameter retrieval tool with no output schema, the description provides the essential ID provenance rule and quota behavior. 'Full details' is somewhat vague but acceptable for a get-by-ID tool; the context is adequate.

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?

The schema already fully describes the id parameter with 100% coverage, including an example. The description repeats this instruction in the IMPORTANT note but adds no new technical detail beyond reinforcing that the ID must come from search results. Baseline 3 is appropriate.

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 uses the specific verb 'Get' with the resource 'full details for a specific funding opportunity', making the function immediately clear. It also implicitly distinguishes from sibling search tools by requiring a specific ID from search results.

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 provides clear usage guidance: use the exact ID from search results, do not guess or construct IDs. It also highlights a benefit (does not count toward monthly searches) that helps the agent decide when to use this tool. However, it does not explicitly name an alternative tool for searching, relying instead on the phrase 'from search results.'

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