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

The description specifies the nature of the return data ('the text'), adding behavioral context that the annotations (readOnlyHint: true) do not cover. It confirms this is a retrieval operation, not a modification.

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 definition is concise, front-loaded, and uses only one sentence to communicate its entire function and acceptable input formats, ensuring maximum information density.

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 simple, read-only tool with a single parameter and no complex output schema, the description provides all necessary information for an agent to understand its scope, inputs, and fundamental purpose.

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?

While schema coverage is 100%, the description is crucial here as it defines the semantic meaning of the 'id' parameter—that it accepts either a system-generated search ID or a raw external URL. This distinction is critical for correct invocation.

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 title and description clearly state the tool retrieves content ('Returns the text') specifically from 'Compound Mint,' which distinguishes it clearly from the surrounding calculation and search tools.

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 context on the permissible inputs, specifying that the ID can come from a search result or be a URL. This implies a usage pattern, though it doesn't explicitly mandate a pre-call to the `search` tool.

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