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

Annotations already mark it read-only and closed-world, and the description adds substantive traits on top: a 24 KB input ceiling, truncation to the first 100 transactions, and a 20 calls/hour rate limit. These are exactly the operational constraints an agent cannot get from the schema, though nothing is said about error behavior on oversized input.

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?

A single tight sentence front-loads the demo framing, then packs input limit, return shape, and rate limit without a wasted word.

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?

With no output schema, the description usefully sketches the return (first 100 transactions plus an analysis preview) and discloses size and rate limits. It leaves 'analysis preview' undefined, but for an 8-param read-only parser this is close to sufficient.

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% with 8 well-documented parameters including enums for format, decimal, and dateFormat, so the schema carries the semantics. The description adds no parameter-level detail beyond 'normalized JSON', making the baseline 3 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?

States a specific verb and resource (parse a statement into normalized JSON) and immediately scopes it as a 'Free demo' with a 24 KB limit, which implicitly sets it apart from the full parse_statement sibling. It stops short of naming that sibling explicitly, so the differentiation is inferred rather than stated.

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 'Free demo' framing and the 24 KB / 100-transaction caps imply this is for quick trials while parse_statement handles production volume, but the description never says when to choose it over convert_statement or analyze_statement. Usage is implied, not directed.

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