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

With no annotations, the description carries the behavioral burden and does so well: it discloses the cost model (free with any API key, otherwise $0.01 per call in USDC), the chains supported (Base, Solana), and the x402 payment mechanism in _meta. It does not detail rate limits or the exact return shape beyond the two resolved fields.

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 front-loaded sentences: the purpose and downstream use come first, followed by the pricing/auth detail. The x402 payment instructions are verbose but earn their place given no annotations exist to convey auth requirements.

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 resolver with no output schema and no annotations, the description covers purpose, downstream usage, and the full payment/auth path. It is nearly complete; only a note on what happens with ambiguous or unmatched queries is absent.

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% for the single 'query' parameter, but the description compensates by explaining what a query may contain (a compound, material, or research topic) and what it resolves to. It adds meaning the bare string schema lacks, though it gives no format examples or edge-case handling.

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 gives a specific verb+resource ('resolve a free-text query... to its subject_type/subject_id') and clarifies the input domain (compound, material, or research topic). It also names the downstream sibling it feeds (get_subject_ri), which distinguishes it from the get_* tools that require an existing ID.

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?

It clearly positions the tool as a pre-step before get_subject_ri, so the agent knows the workflow context. It does not explicitly state when NOT to use it (e.g., when an ID is already known), but the routing intent is unambiguous.

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