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

No annotations are provided, so the description carries full burden for behavioral disclosure. It mentions results are grouped by type but does not address pagination, rate limits, case sensitivity, error handling, or read-only nature. For a search tool, these are significant gaps.

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 sentences, no fluff, and front-loaded with the action and purpose. Every word earns its place.

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, the description should hint at return format. It says 'results grouped by type' but does not specify structure, pagination, or error cases. It is adequate for a simple search tool but could be more complete, especially regarding return details.

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 100%, so the baseline is 3. The description adds context about grouping results and fetching single records, but does not clarify the types parameter format beyond what the schema provides. No additional semantics for individual 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 'Search a keyword across every Cure Cancer With AI dataset at once' and lists the specific dataset types, using a specific verb and resource. It distinguishes itself from siblings by advising to use this first for broad discovery and then fetch a single record, implying it is a cross-dataset search tool.

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 explicit usage guidance: 'Use this first for broad discovery, then fetch a single record by id/slug/nctId for full detail.' This tells when to use this tool and when to use the sibling get_* tools. However, it does not explicitly contrast with other search tools like search_compounds.

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