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

The description confirms the read nature of the tool by stating 'Rows on record,' which aligns with the provided annotations. It does not introduce new behavioral risks or complex operational details beyond standard retrieval 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?

The description is extremely concise, using two short sentences where every word contributes functionally. The information is front-loaded and highly efficient.

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 retrieval tool, the description is complete as it defines what the returned rows represent (records with filters) and the sorting logic (newest first). No major operational gaps like pagination or required state are noted.

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?

The schema coverage is 100%, setting the baseline at 3. The description adds specific semantic meaning to the 'unreviewed' status, explaining what it signifies operationally, which adds value beyond simple schema definitions.

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 retrieves transaction rows, indicating its purpose as a data retrieval function. It is less effective at differentiating itself from highly numerous siblings compared to a perfect score, but the combination of the name and the description is clear.

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 provides high-value usage guidance by explaining the operational context of the 'unreviewed' status—that it indicates items needing attention. This tells the agent precisely when and why to apply that specific filter.

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