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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantive behavior the agent cannot infer: $2 USDC per call via x402, no charge when too few sources answer, and that with async=true the core source is verified before the job is queued and charged. This is exactly the billing/async disclosure an agent needs before invoking a paid tool.

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-loads the user-facing question and then the report contents, followed by billing/async notes. Dense but largely waste-free; the charging rule is stated twice (general no-charge and async-specific), a minor redundancy.

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 paid, async-capable, webhook-delivering tool with no output schema, the description covers deliverables (verdict, score, PDF), the async job flow, and the cost model. It stops short of describing pagination/rate limits or expected latency for the sync path, but nothing critical to calling it correctly is missing.

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 adds meaning beyond the schema: it explains pdf as a 7-day link, that async=true still performs a pre-queue core-source check, and that webhook_url posts the finished report. The async pre-check detail in particular goes past 'Return a job id now'.

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?

Names a specific verb+resource (repository report) and enumerates exactly what it covers: adoption/maintenance metrics, license, OSV dependency vulnerabilities, and an AI code review of the entry file. Easily distinguished from siblings like report_company, report_domain, or report_token by the open-source-dependency framing.

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 opening question ('Should you depend on this open-source project?') gives clear intent for when to reach for it, and it explains the async path and the no-charge failure condition. However, it names no alternative sibling (e.g. github, code_review, vulns) for narrower lookups, so the routing guidance is incomplete.

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