Pentagonal

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

No annotations are provided, so the description carries full burden. It mentions the tool 'returns the complete fixed contract,' which implies a read/write operation, but doesn't disclose critical behavioral traits like whether it modifies the original code in place, requires specific permissions, handles errors, or has rate limits. For a mutation tool with zero annotation coverage, this is a significant gap.

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 a single, well-structured sentence that front-loads the purpose ('Fix a specific vulnerability in a smart contract') and efficiently covers inputs and outcomes. Every word earns its place with no redundancy or fluff.

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 complexity of smart contract vulnerability fixing, no annotations, and no output schema, the description is incomplete. It lacks details on behavioral aspects (e.g., error handling, safety guarantees), output format (e.g., whether it returns only code or includes explanations), and doesn't compensate for the absence of structured fields, leaving gaps for an AI agent.

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 three parameters ('code', 'finding_title', 'finding_description') with clear descriptions. The description adds no additional meaning beyond what the schema provides, such as format examples or constraints, meeting the baseline for high schema coverage.

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 ('Fix a specific vulnerability'), the resource ('smart contract'), and the outcome ('returns the complete fixed contract preserving all existing functionality'). It distinguishes itself from siblings like 'pentagonal_audit' (which likely identifies vulnerabilities) and 'pentagonal_generate' (which likely creates new contracts) by focusing on remediation.

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 when a vulnerability is known ('Provide... the finding details'), suggesting it's for post-audit fixes rather than initial auditing or generation. However, it doesn't explicitly state when not to use it (e.g., for new contract creation or without a specific finding) or name alternatives like 'pentagonal_audit' for vulnerability detection.

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