Repositories

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorld=true), and the description adds non-derivable behavior: that calls may consume paid API credits, that confirm=true is required, and that the read-like POST does not publish to social platforms. It stops short of covering error handling, failure modes, or rate-limit specifics, so it is strong but not exhaustive.

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?

Front-loaded with the core action and returned fields, then a second paragraph for identity inputs and the cost/confirm caveat. Two sentences carry the load with no filler; the final sentence about social-platform publishing is slightly defensive but still earns its place as behavior disclosure.

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 an 8-parameter, no-required-param, no-output-schema list tool, the description covers the returned metadata, the identity inputs, pagination, and the credit/confirm constraint. Combined with a fully documented schema and existing safety annotations, an agent has everything needed to call it correctly.

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 100%, so every parameter (url, handle, account, cursor, type, sort, direction, confirm) is already documented in the schema with enums and defaults. The description restates the identity inputs and pagination but adds no syntax or format detail beyond the schema, so the baseline of 3 is appropriate.

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 ('Retrieves a user's public repositories') and enumerates the returned metadata (description, language, stars, forks, topics, license, visibility, default branch, timestamps). The scope clearly separates it from the singular github_repository and from github_user, but the description never names those siblings, so it stops just short of explicit differentiation.

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?

It tells the agent how to supply an identity ('Pass username, handle, or url') and that pagination uses a cursor, which implies usage. However it never states when to choose this over github_repository, github_user, or github_trending_repositories, and gives no prerequisites or exclusions, so selection guidance must be inferred from the name.

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