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

The description discloses important behavioral traits beyond annotations: it is deterministic static analysis with no LLM in the hot path, runs in seconds, returns HTTP 402 until payment is presented, and payments are final/non-refundable. It also clearly warns about the tool's limitations (flags fixed code as often as vulnerable). The only minor gap is not detailing exact output structure, but the description already covers the key behavioral caveats.

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 dense but well-organized, front-loading the payment terms and then the core functionality. The untrusted-provider-content wrapper adds some noise, but the actual content is structured with clear sections. It earns its length given the payment warning and the important NOT-a-vulnerability-detector caveat.

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 tool with 2 params, 100% schema coverage, and no output schema, the description is quite complete. It covers input format, behavior, limitations, alternatives, and payment terms. It could be slightly more explicit about the exact response format, but the description already lists the flag fields (severity, CWE, file:line, code evidence, suggested fix, counts).

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 schema already documents both parameters. The description adds context that repo can be owner/name or a GitHub URL and ref defaults to master, but this mostly aligns with the schema. Baseline 3 is appropriate since the schema does the heavy lifting.

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 a static pattern scan of a Solana/Anchor Rust repository, taking a repo owner/name or GitHub URL and returning flagged risky code shapes. It explicitly distinguishes itself from sol-quick-scan and from fetching a single file, so an agent can tell it apart from siblings.

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 says when to use this tool vs alternatives: use sol-quick-scan for one-line risk triage of one contract, and fetch a file yourself to read a single known file. It also warns this is NOT a vulnerability detector and should be used to find spots for human review, never as an audit verdict.

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