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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), so the description earns credit for disclosing a return-value trait beyond the schema: that it also returns whether the escrow was deployed via the protocol factory. With no output schema, this extra disclosure is genuinely useful; it stops short of describing fee format, units, or aggregation behavior.

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?

Three short sentences, front-loaded with the primary action, then the secondary return value, then the use case. No filler, though the third sentence is more motivational than operational.

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 read-only, single-parameter tool with no output schema, the description covers the action, a notable extra return field, and a motivation. It is nearly sufficient; minor gaps remain around fee units/format and whether values are per-escrow or cumulative.

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% for the single escrowAddress parameter, so the schema already carries its meaning. The description adds nothing beyond restating that the address identifies 'a specific escrow contract', which is the baseline case for a fully documented single-parameter tool.

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?

States a specific verb and resource ('Get protocol fees collected from a specific escrow contract'), clearly differentiated from the protocol-wide siblings like protocol_fee and protocol_token_fees by its escrow-scoped framing. It doesn't explicitly name those siblings, so an agent must infer the distinction rather than being told it.

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?

'Useful for auditing fee flows' implies a usage context but gives no when-to-use/when-not guidance and does not route the agent to alternatives such as protocol_fee or get_escrow. The condition that selects this tool over its siblings is left implicit.

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