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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses what the response contains (stats, capabilities, best-for, limitations, alternatives), but says nothing about being a read-only lookup, behavior on unknown slugs, or rate 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?

A single front-loaded sentence: verb, resource, identifier source, then the returned fields. No filler or restatement of the 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?

With no output schema and no annotations, the description compensates by enumerating the returned fields, which is adequate for a simple one-parameter getter. Error behavior and read-only status remain unstated but are minor for this shape.

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 define 'slug'. It does: the identifier comes from search_tools, which tells an agent where to get a valid value — meaning beyond the bare 'string' type in the schema.

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 (get details for one tool by slug) and enumerates the payload: GitHub stats, capabilities, best-for, limitations, alternatives. It does not explicitly separate itself from the sibling get_alternatives, which the mention of an 'alternatives' field could blur, so it falls short of a 5.

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)' establishes the pipeline: discover a slug with search_tools, then fetch its details here. That is clear context for when to reach for this tool, but no explicit when-not case or direct comparison to get_alternatives is offered.

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