repo_security_posture

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

No annotations are provided, so the description carries the full burden. It does disclose the analysis outputs and uses 'recommends' and 'lists' to imply a read-only advisory operation rather than a mutating one, but it never states that no files are modified, whether a git repository is required, or whether the analysis is expensive/slow for large repos.

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?

A single front-loaded sentence with the core purpose first and the deliverables after. The parenthetical area list (auth, payments, PII, admin, API, infrastructure) is dense but each item earns its place by telling the agent what the scan covers.

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 no output schema and no annotations, the description must carry more weight. It partially compensates by enumerating what the analysis reports, but it does not describe the shape of the result, the guard-mode concept it references, or how the recommended fixes relate to the fix_code/remediation_plan siblings.

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 100% with only two simple parameters ('path' as repository root, 'format' enum with default), so the schema already does the work. The description adds nothing about path expectations (absolute vs relative, monorepo roots) or when to choose JSON over markdown, so it stays at baseline.

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?

States a specific verb and resource ('Analyze a repository's overall security posture') and enumerates the concrete artifacts produced (sensitive-area map, high-risk workflows, guard-mode recommendation, priority fixes). This clearly reads as an aggregate/overview analysis rather than a single-target scan like scan_secrets or check_dependencies, though it never names a sibling explicitly.

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 'overall security posture' framing implies this is a high-level entry point rather than a targeted check, which is enough to distinguish it in spirit from scan_file or check_code. However, with near-identical siblings like full_audit, deep_scan, and security_workflow present, the description gives no explicit when-to-use or when-not-to-use guidance.

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