Check Breach Readiness

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

No annotations are supplied, so the description carries the full burden. It usefully discloses the authorization requirement and defensive intent, which is real behavioral context, but it never states whether the operation is read-only, what document types it looks for (e.g., SECURITY.md, incident response plans), or whether anything is written or cached. For a documentation-scanning tool with zero annotation coverage, those gaps keep it at minimum-viable-plus.

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 purpose is front-loaded in a single clear sentence, but the remaining three clauses are substantially redundant: 'Use only on sites/projects you own…', 'Defensive use only', and 'Use this tool only on websites, endpoints, or local projects that you own…' restate the same authorization condition. Collapsing them into one sentence would lose no information.

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 an output schema present, the description needn't explain return values, and with a single scalar parameter the surface area is small. Purpose plus the explicit authorization/defensive-use constraint covers what an agent needs before calling it; only the read-only question and the meaning of 'documentation' remain unstated.

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% for the single required 'path' parameter, so the schema provides no semantics on its own. The description partially compensates by indicating the target may be 'websites, endpoints, or local projects', implying path accepts a URL or a local filesystem path, but it never states the accepted format or a concrete example.

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 uses a specific verb ('Audit') and a specific resource ('repository documentation for breach response readiness and security contacts'), so the agent knows exactly what the tool inspects. It does not name or contrast with any sibling tool (e.g., run_full_audit or scan_project_files), so the scope distinction is left implicit.

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?

It gives strong usage restrictions ('only on sites/projects you own or are authorised to audit', 'defensive use only') but these are authorization constraints, not selection guidance. Nothing tells the agent when to pick this over run_full_audit or generate_gap_report, so the when-to-use choice among siblings is only implied by the tool name.

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