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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavioral context about billing and that repeat requests may repurchase data — but it undercuts that value with internally contradictory pricing ('at least 10 Nexscope credits' versus '1 credit per request'), which is not an annotation contradiction but leaves the cost model ambiguous.

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 first two sentences are tight and front-loaded, but the remainder is boilerplate pricing filler that repeats the same claim twice and states two conflicting prices. Roughly half the text is promotional/administrative noise rather than tool guidance.

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, the field enumeration usefully describes what comes back, and input format is covered. What is missing for a paid, single-resource lookup is unambiguous cost behavior and any pointer to sibling tools for listing or discovery use cases.

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%, so the single 'url' parameter is already documented. The description only adds the qualifier that a 'full' repository URL is required, a marginal clarification beyond the schema, which matches the baseline 3 for fully documented schemas.

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 description opens with a specific verb and resource ('Retrieves public metadata for one GitHub repository') and enumerates the returned fields (owner, stars, forks, topics, license, default branch, open issues, timestamps), so its function is unmistakable. It does not explicitly distinguish itself from siblings such as social_github_user_repositories or social_github_trending_repositories, which keeps it from 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?

'Pass a full GitHub repository url' is an invocation directive, and the field list implies this is a single-repo lookup rather than a listing or trending operation. However, there is no explicit when-to-use or when-not-to-use guidance naming the sibling repository tools as alternatives, so the routing signal is only implied.

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