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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new context beyond the annotations: a fixed api.github.com destination and no token/auth requirement, which tells the agent this works unauthenticated against a known host.

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?

Two short sentences with the scope constraint front-loaded and zero filler. 'Contribution links' is slightly vague, but the sentence still earns its place.

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 two-parameter read-only tool with full annotations, the description covers scope, host, auth, and result kind ('metadata and contribution links'). With no output schema, slightly more detail on what metadata fields are returned would help, but nothing essential to invoking it correctly is missing.

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 0%, so the description must compensate, and it says nothing about `owner` or `repo`. The names are largely self-explanatory, which keeps this at minimum-viable rather than failing, but there is no guidance on format (case sensitivity, max length, or that they form an owner/repo pair).

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: reads public GitHub repository metadata and contribution links. The 'public' qualifier distinguishes it from any private-repo sibling, though none exists among the sibling tools, so no further differentiation is required.

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?

Implies usage (fetching metadata for a public repo) and includes an implicit exclusion ('no private repositories'), but does not state when an agent should reach for this versus other tools or note any prerequisites beyond 'public'.

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