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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description doesn't need to repeat safety traits. It adds context about the exact metrics returned (request count and bandwidth) and acceptable period values, but does not disclose potential limitations like data granularity or default period behavior.

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 description is a single, well-structured sentence that front-loads the core functionality. Every word adds value, with no redundancy or fluff.

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?

Given the tool's simplicity, the read-only annotations, and the presence of an output schema, the description fully covers what the tool does. Minor gaps like default period or data freshness are not critical for a safe, read-only operation with clear input examples in the schema.

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?

With 0% schema description coverage, the description must clarify parameter meaning. It does explain that owner/repo refer to a GitHub repository and enumerates valid period values, but it does not specify a default period or provide format constraints beyond that. This is a reasonable but partial compensation for the schema gap.

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 clearly states the tool returns JSDelivr CDN request count and bandwidth for files served from a GitHub owner/repo. It includes the verb 'Return' and specifies the resource and metric, distinguishing it from sibling tools like npm_package_stats.

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 description implies usage when the user needs CDN statistics for a GitHub repository and allows specifying a period. It does not explicitly mention alternatives or exclusions, but the unique focus on GitHub repos provides clear context for when to use it.

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