comptext_rust_audit

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

The description explicitly states 'safe read-only', disclosing non-destructiveness. However, no annotations are present, so the description carries the burden. It does not detail what checks are performed, error behavior, or prerequisites, leaving gaps in 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 a single sentence with no wasted words, but it is too brief to be fully useful. It sacrifices informativeness for brevity, resulting in a structure that could be expanded with key details while remaining concise.

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 presence of three parameters and an output schema, the description is insufficient. It does not explain the tool's role within the sibling context, the meaning of parameters, or expected outputs. The tool's complexity demands more context for effective agent usage.

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 0%, meaning the schema itself provides no descriptions for the three boolean parameters (check, clippy, tests_no_run). The tool description fails to explain any parameter semantics, leaving the agent without guidance on how to use them.

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?

Description states 'Run safe read-only Rust checks', which clearly identifies a specific verb (run), resource (Rust checks), and a key trait (read-only). This distinguishes it from sibling tools that focus on contracts, packaging, etc.

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?

No guidance is provided on when to use this tool versus alternatives like comptext_contract_check or comptext_github_pack. The description implies usage for Rust auditing but lacks explicit context or exclusions.

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