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

Annotations already mark readOnlyHint=true, and the description adds substantial behavioral context: Bearer key auth, the 25-item batch cap, one verdict per item plus a summary line, and per-item evidence, source, and read date. This goes well beyond the annotation without contradicting it.

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-load the core purpose before covering auth and output behavior. Every clause contributes useful information and there is no filler.

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 still sketches the response shape: one verdict per item, a summary line, evidence, source, and read date. It also covers auth and limits. Exact response formatting and error behavior are left to inference, but the essential guidance is present.

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 already documents item kinds, value constraints, thresholds, and restrictions; the description mainly reinforces the batch size and gives examples of subjects. With schema coverage around 67%, the description adds context but does not meaningfully enrich parameter semantics beyond the schema.

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 opens with a specific verb and resource ('Rule a set of items at once') and gives concrete use cases (recipe ingredients, basket, several days). It clearly distinguishes itself as a batch operation from siblings like check_item by emphasizing 'at once' and the 25-subject limit.

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 clear context for when to use the tool: when multiple subjects should be checked in one call. It also notes the auth prerequisite and points to register for creating a key, but it does not explicitly name alternatives or state when not to use it.

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