check_security

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

Discloses read-only, no auth required, potential 60s delay for first scan, and return value composition. No annotations exist, so description carries burden. Lacks details on error handling if both params provided or 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?

Four sentences, each informative: purpose, return format, parameter guidance, usage context, timing info. No redundancy.

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 all aspects: purpose, input, output (return values), behavior (read-only, timing), and usage guidance. No output schema, but description sufficiently explains return. Completeness is high.

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 descriptions. Description adds value by clarifying mutual exclusivity and contexts for each parameter (AgentGraph entities vs any repo).

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 clearly states verb 'Check' and resource 'security posture of an agent or GitHub repo'. It distinguishes from siblings by specifying vulnerability findings categories and trust score, which is unique among related tools.

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 says 'Use before installing or interacting with third-party tools' and 'Provide either entity_id OR github_url'. Could mention not to use for other purposes or when to use alternatives, but current guidance is sufficient.

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