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

Annotations already indicate safe, read-only behavior. Description adds crucial context: search results are candidates only, must verify with get_opportunity; explains filter combination logic (OR within arrays, AND across fields). No contradiction with annotations.

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 packing essential information: purpose, strategy, filter logic, and post-search action. Every sentence earns its place, and key guidance is front-loaded.

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?

Despite complexity (32 parameters, many filters), the description covers the core behavioral rules and references sibling tools. Output schema exists, so return values are handled separately. Complete for effective agent use.

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 59%, so description carries some burden. It adds meaning beyond schema by explaining how filters combine and referencing list_filter_options for exact values. However, with 32 parameters, it doesn't detail each one individually, but the schema compensates with per-parameter descriptions.

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?

Clearly states the tool searches for published public fellowships, grants, scholarships, prizes, and funded residencies. Provides strategic guidance on how to search (start broad, avoid stacking filters) and distinguishes from siblings get_opportunity and list_filter_options by specifying this is for initial discovery.

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?

Explicitly advises to start with separate broad calls, not to stack sparse filters, and to use list_filter_options. Also directs to call get_opportunity before ranking or citing results. This gives strong when-to-use and when-not-to-use guidance.

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