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

Annotations already declare readOnly, openWorld, and idempotent, so the safety profile is covered. The description adds real value by enumerating the returned payload (description, stars, install command, remote endpoint, license, tags, last commit), which is critical since there is no output schema.

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?

A single front-loaded sentence with no filler; the identifying key appears first and the field list is compact.

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 one-param lookup with no output schema, the description compensates by listing the returned fields, so the agent knows what it will get. Missing only edge behavior such as what happens for an unknown slug.

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% with a pattern and example, so the baseline is 3. The description adds provenance the schema cannot express — that the slug originates from search_tools — which helps the agent construct a valid value rather than invent one.

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 ('Full details for one tool') with the exact key ('slug'), and names the sibling that produces that key (search_tools), so an agent can distinguish it from list_best, search_tools, and trending immediately.

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 parenthetical '(from search_tools)' tells the agent when this tool is applicable and what feeds it, which is meaningful routing guidance. It stops short of an explicit when-not clause (e.g. use search_tools to find slugs rather than guessing them).

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