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

Annotations only supply readOnlyHint=false and idempotentHint=false; the description must carry the rest and does not. It never warns that 'update' can archive a repo or flip visibility (irreversible-ish, non-idempotent in effect), never mentions permission/owner requirements for org creation, and says nothing about rate limits. Naming visibility and merge options as updatable is the only behavioral signal.

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 short sentences, front-loaded with the resource and the valid verbs, then the per-action routing. No filler, no restatement of the title, and each sentence carries distinct information.

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 29-parameter, mixed read/write tool with no output schema and thin annotations, the description is minimally viable: it routes the actions and names update categories, while the schema documents per-action parameter requirements. It omits return shape, pagination behavior, and any error/permission context, so an agent still infers a fair amount.

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 baseline is 3, but the description goes further by explaining the semantics of the required action enum (poorly served by the schema's 'Operation to perform') and grouping which field families apply to update. Minor ding: it cites 'visibility', a parameter that does not exist in the schema (the actual property is 'private').

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 resource (repositories) and enumerates the three operations (list, create, update) with a one-clause gloss of each. It is trivially separable from siblings like branches, issues, or pull_requests, and internally the three actions are spelled out rather than lumped into 'manage'.

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?

Gives explicit action routing: 'list' for your repositories, 'create' for a new one (account or org), 'update' for settings changes. It covers the main selection question (which action), but offers no guidance on list filtering, pagination, or when to reach for a search tool instead.

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