Pentagonal

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

With no annotations provided, the description carries the full burden. It effectively discloses key behavioral traits: the 8-agent specialization, that findings include severity ratings and line numbers, and that rules are learned automatically. However, it doesn't mention performance aspects like execution time or resource requirements.

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 front-loaded with the core purpose, followed by supporting details about agents and outputs. Every sentence adds value: the first defines the action, the second lists specializations, the third describes outputs, and the fourth explains rule learning. No wasted words.

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?

Given the tool's complexity (multi-agent security testing) and no output schema, the description does well by specifying the attack vectors and output format (severity ratings, line numbers). However, it could better address error cases or limitations (e.g., contract size constraints).

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%, so the schema already documents all parameters thoroughly. The description doesn't add any parameter-specific details beyond what's in the schema (e.g., it doesn't explain code format or chain implications). Baseline 3 is appropriate when the schema does the heavy lifting.

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 the specific action ('Run an 8-agent security pen test') on a specific resource ('smart contract'), and distinguishes it from siblings by detailing the specialized attack vectors (reentrancy, flash loans, etc.). It goes beyond the tool name to explain the multi-agent approach and output format.

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 smart contract security auditing but doesn't explicitly state when to use this tool versus alternatives like 'pentagonal_fix' or 'pentagonal_rules'. It mentions 'New security rules are automatically learned', which hints at iterative use, but lacks clear guidance on prerequisites or exclusions.

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