repo_security_posture

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

No annotations provided, but description explains the tool analyzes and recommends (no mutation implied). However, it does not disclose if the tool modifies the repository, requires specific permissions, or has rate limits.

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?

Two efficient sentences. First sentence states the core purpose, second lists key outputs. No wasted words, front-loaded with essential 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?

For a tool with two simple parameters and no output schema, the description adequately states what it maps, identifies, and recommends. However, it does not describe the return format beyond the format parameter, nor explain 'guard mode' or how priority fixes are presented.

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 covers 100% with clear descriptions for both parameters. Description adds context about what the tool examines (sensitive areas list) but does not provide additional details about the parameters beyond what schema includes.

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 a clear verb+resource ('Analyze a repository's overall security posture') and lists specific outputs (maps sensitive areas, identifies high-risk workflows, recommends guard mode, priority fixes). It distinguishes from siblings like 'deep_scan' and 'compliance_report' which have different scopes.

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 explicit guidance on when to use this tool versus alternatives. Does not mention prerequisites, when-not-to-use, or contrast with sibling tools like 'deep_scan' or 'compliance_report'.

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