Take a P2P offer

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

The description adds significant behavioral context beyond annotations: it explains the on-chain mechanism (pinning exact terms), the binding nature of the commitment, and the requirement for a signing key. Annotations already indicate non-read-only, open-world, idempotent, and destructive hints, but the description enriches these with practical implications.

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 two sentences, both impactful. The first front-loads the mechanism and benefit, the second adds consequences and requirements. No unnecessary 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 complexity of an on-chain loan activation tool with no output schema and two parameters, the description covers purpose, behavioral traits, and a key requirement (signing key). It could mention failure modes or return values, but overall it is sufficiently complete for an 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 covers 50% of parameters (id has description, chain lacks description). The description does not elaborate on parameter meaning or provide usage details for the parameters, so it does not compensate for the missing schema description. Baseline 3 is appropriate.

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 tool accepts an open offer and activates a loan, using specific verbs ('Accept', 'pinning', 'Approves and escrows'). It distinguishes itself from sibling tools like p2p_create_offer and p2p_cancel by focusing on taking an existing offer.

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 use when accepting an open offer and mentions a signing key requirement, but lacks explicit when-to-use or when-not-to-use guidance compared to alternatives like p2p_repay or p2p_cancel. No exclusions or comparisons are provided.

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