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

Beyond the annotations (readOnlyHint, openWorldHint), the description explains what the open-world operation actually does: it performs a network fetch, retrieves specific metadata fields (exists, language, description, topics, stars, last push), conditionally cross-checks against portfolio records, and optionally returns README text. This adds substantial behavioral context and does not contradict the annotations.

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 compact and front-loaded with the core purpose. Each sentence adds something: the verification process, the readme option, and the concrete usage scenario. The first sentence is slightly dense with parenthetical details, but there is no redundant filler beyond briefly restating the annotations.

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 that there is no output schema, the description compensates by enumerating the metadata fields returned and describing the README behavior. It also covers the cross-check condition and the intended use case. It doesn't specify error handling or the exact shape of a repo-not-found result, but the coverage is strong enough for an agent to invoke the tool 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 already 100%, setting a baseline of 3. The description goes further by clarifying that repo can be a bare name with owner defaulting to ManSio, a full owner/name pair, or a GitHub URL — details not present in the schema. It also adds the ~1200 character README truncation behavior for readme=true.

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: 'Verify a GitHub repository against the primary source'. It then details the exact mechanism — fetching metadata from the GitHub API and cross-checking it with the portfolio record — and distinguishes itself from generic claim-verification tools by focusing on repository facts. The readme:true behavior reinforces the unique scope.

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 gives explicit usage direction: 'Use it to ground claims like "the repo is Python" or "he maintains mscodebase-intelligence" with live data instead of trusting the claim.' This clearly communicates when to invoke the tool. It does not explicitly mention when not to use it or name sibling alternatives such as verify_claim, but the repo-specific context makes the intended scope clear.

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