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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantial behavior beyond that: the 0.25 USDC x402 charge per call, that unpaid calls return a PaymentRequired (isError) result, the exact retry mechanism via params._meta['x402/payment'], and that charging occurs only on delivery. This is exactly the kind of cost/auth/error context annotations cannot carry.

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?

Long but well front-loaded: price and payment model lead, then the scope, then the feature enumeration, then the payment retry mechanics. The feature list is dense and slightly crowded, but each item is a distinct check that differentiates the paid tier, so very little is pure padding.

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?

With no output schema, the description must convey what comes back, and it does: a 0-100 risk score, concrete next steps, and a detailed enumeration of inspected artifacts. Payment failure and retry paths are covered, so an agent has everything needed to call it and handle the response.

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 all three parameters are already documented, including the 1-3 comma-separated form and the optionality of repos and command. The description restates the '1-3 repos per call' constraint and clarifies that command is one you plan to execute, but adds no syntax or format detail beyond the schema. Baseline 3 applies.

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 ('Full pre-run security report for a GitHub repo') with explicit scope (1-3 repos per call) and positions itself against the sibling by saying it does 'Everything check_repo does, plus:' followed by an enumerated feature list. An agent can distinguish it from check_repo without opening either schema.

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 a clear usage context ('for AI coding agents about to clone it and run its install steps') and implicitly routes lightweight needs to check_repo via the 'Everything check_repo does, plus' framing. It does not explicitly say when to use the free-ish siblings (check_repo, check_command, full_report_info) instead, and the optional command parameter's relationship to check_command is left unstated.

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