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

Annotations only cover readOnly/openWorld; the description adds genuinely new context: that only public data is returned, that the call costs 1 credit, and how GitHub's raw fields surface (stars→likeCount, forks→shareCount, issues/PRs→openIssuesCount). The field mapping is especially valuable because 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?

Three front-loaded sentences with no filler; purpose first, then returned fields, then cost. The field-mapping sentence is dense but earns its place given no output schema.

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 tool the description covers what data comes back and the credit cost, which compensates for the missing output schema. But it leaves the second parameter (`cache_max_age`) unexplained and gives no hint about response shape or error behavior for invalid repo identifiers.

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 only 50%. `url` is documented in the schema but the description adds nothing about accepted formats, and `cache_max_age` is completely undocumented in both schema and description. With low coverage the description should compensate, and it does not.

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/resource ('Repository details') and enumerates exactly which fields are returned (stars, forks, open issues, topics, language, licence), which distinguishes it from github_trendingRepositories and github_userRepositories by scope. It stops short of explicitly naming those siblings, so a 4 rather than 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?

Usage is only implied: given a repo URL/owner-slug, fetch its details. There is no statement of when to prefer this over github_userRepositories or github_trendingRepositories, nor any exclusions or prerequisites beyond 'public'. Adequate but leaves routing to inference.

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