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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered. The description adds useful context beyond annotations by saying results are ranked best-match-first and summarize suppliers, price, and carbon footprint. It omits behavior such as result limits, pagination, or handling of no matches.

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 compact sentences, front-loads the core action and accepted query types, and uses the second sentence to describe results and ordering. There is no filler or redundant restatement of the tool name.

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?

An output schema exists, so the description need not fully explain return values, and annotations cover read-only and open-world status. The description adequately explains search inputs and result shape, though it could be more complete by mentioning the limit parameter and search matching behavior.

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 0%, so the description must carry parameter meaning. It does this well for the query parameter by listing accepted identifier types, but it says nothing about the limit parameter or its default behavior, leaving half the parameters undocumented.

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 states a specific verb and resource ('Find compounds on SharpSyn') and enumerates the identifier types it accepts, making the operation clear. It does not explicitly distinguish itself from the sibling get_compound, so sibling differentiation is only implied by the plural search framing.

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 this is the search tool for locating compounds by various identifiers, which helps an agent choose it over get_compound. However, it never states when to use this versus retrieval by a known identifier, nor does it mention exclusions or alternatives.

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