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

With no annotations, the description carries the behavioral burden. It discloses the cost ($2.5 per call), which is critical for an agent to weigh invocation, and enumerates the exact outputs (last 5 commits, contributor count, etc.). It does not mention side effects or data persistence, but since this is a read-only lookup, the explicit list of outputs provides strong transparency.

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 concise (two sentences) and front-loads the cost and purpose. The list of outputs is efficiently crammed into one sentence. It could be slightly more compact, but every word adds value—no fluff. Good structurungal though the parameter ambiguity hurts slightly.

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 has a single parameter, no output schema, and no annotations, the description does a good job of providing context. It covers what the tool does, why to use it, and cost. Missing details about how to specify the repo (the 'q' format) and what the output structure looks like, but these are not critical for an agent to decide whether to use it. Overall, it is nearly complete for an initial decision.

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?

The schema defines only one parameter 'q' with a generic description ('JSON or key=value input'), leaving the format and intended content ambiguous. The description does not explain how to specify the repo, but given the schema coverage is 100% (though shallow), the description partially compensates by clarifying the tool's scope. The gap is that the parameter format is not detailed, but the tool's purpose is clear enough.

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 performs GitHub repository due-diligence and lists specific data points included (snapshot, commits, contributor count, archived flag, etc.). It uses a precise verb ('due-diligence') and resource ('GitHub repo'), and differentiates itself from siblings by focusing on repo trustworthiness, unlike e.g., github_repo or web_fetch.

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 explicitly states when to use: 'Use to decide whether to depend on or contribute to a repo before trusting it.' This gives clear context for use. It does not explicitly name alternatives or say when not to use, but the purpose is specific enough that an agent can infer it should be used for repo trust assessment, not for general repo browsing.

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