check_secrets

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

Adds beyond annotations: 'No data stored' and suppression of generic password rule when specific fires. Annotations already declare readOnlyHint, idempotentHint; no contradiction.

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?

Single paragraph but every sentence provides value (purpose, usage, behavior, limits). Could be slightly more structured but 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?

Covers use case, supported languages, alternatives, rate limits, output format, data retention, and rule suppression. Output schema mentioned, so complete.

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%; description adds no extra meaning beyond schema for 'code' and 'language'. Baseline 3 is appropriate.

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 starts with clear verb 'Scan' and specific resource 'source code for hardcoded secrets', lists types and languages, and distinguishes from sibling 'check_injection'.

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?

Explicitly states when to use ('detect leaked credentials before commit'), provides alternative ('for injection detection use check_injection'), and mentions rate limits.

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