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

With no annotations, the description carries the full burden. It does disclose useful behavior: a 200-name cap, that results come back as an audit-ready summary with list version and timestamp, and the 'PRO' tag hinting at a premium tier. It says nothing about authentication requirements, rate limits, or what happens when the cap is exceeded.

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 that front-loads the batch capability; almost every clause carries information. The 'PRO' prefix is minor noise but the rest is 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?

There is no output schema, and the description partially compensates by describing the return summary (list version, timestamp, audit-readiness). However, for a screening tool with an access_token parameter and a near-identical sibling, it omits auth expectations and tool-selection context, leaving meaningful gaps.

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 coverage is 67%, with threshold ('0-100, default 60') and access_token already documented. The description adds the 200-item cap for names and clarifies that threshold is a match threshold, but does not explain threshold tradeoffs or what values of names are acceptable beyond the examples.

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 names a specific verb ('Screen') and resource ('names'), gives the batch cap (up to 200) and example entity types (customers, suppliers, counterparties), which is far more than restating the name. It does not, however, distinguish itself from the very similar sibling 'global_batch_screen', leaving the agent to guess which batch screener applies.

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?

Beyond the implicit hint that this is for multiple names rather than one, there is no when-to-use guidance, no exclusions, and no pointer to alternatives such as counterparty_check, sanctions_check, or global_batch_screen, despite eleven siblings. The agent must infer routing entirely.

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