Scan authorized local repository

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint=false. The description adds value by specifying the nature of checks (Python and secret) and the constraint 'under operator-allowed roots', which goes beyond the annotations. No contradiction exists.

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, front-loaded sentence with no filler. Every word contributes to explaining the tool's core action and constraints, making it highly efficient.

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?

While the output schema exists and annotations cover safety, the description lacks explicit usage guidance relative to siblings and provides no parameter clarification. It is adequate for a simple read-only tool but leaves gaps in operational decision-making.

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 has 2 required parameters with 0% description coverage, so the description must compensate. It does not explain 'path' or 'engagement_id', and only vaguely hints at 'operator-allowed roots'. This is insufficient for understanding what values to pass.

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 'Run' with a clear resource 'built-in read-only Python and secret checks' and a scope 'under operator-allowed roots'. This clearly differentiates it from sibling tools like analyze_headers or health, which address different concerns.

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 implies usage for scanning an authorized local repository, but it does not explicitly state when to use this tool versus alternatives, nor does it mention exclusions or prerequisites. The 'operator-allowed roots' hint provides some context but not enough for clear decision-making.

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