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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds real value beyond that by stating the domain restriction ('Only accepts docs.yield.xyz URLs') and characterizing the return as 'authoritative spec with exact field names, types, and examples', which matters since there is no output schema. It stops short of saying what happens on a non-docs URL (error vs. empty) or any size/pagination limits.

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?

Four short sentences, front-loaded with the identity and purpose, followed by usage, return value, constraint, and exclusion. No filler or 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?

For a single-parameter read tool with no output schema, the description covers what it does, what it returns, the input constraint, and the exclusion case. Nothing an agent needs in order to call it correctly is missing.

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% and the single parameter is documented with an example, so the baseline is 3. The description adds a constraint the schema does not encode — that the URL must be a docs.yield.xyz .md page — which meaningfully narrows what a valid value looks like.

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?

States a specific verb and resource ('fetches the full markdown content of any Yield.xyz documentation page') and labels itself a BUILDER TOOL, which separates it from the live-API siblings like yields_get_all or actions_get. The agent can tell what it returns (markdown docs) without opening the schema.

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?

Gives an explicit sequencing rule ('Use after yield_lookup_docs returns a URL'), naming the sibling that feeds it, plus an explicit exclusion ('Do NOT use this for live API calls or user transactions'), which routes the agent away from the transaction/query tools. Both the when and the when-not are present.

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