workers_readyreply_list

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

With no annotations provided, the description carries the full burden. It only states the listing/filtering behavior but doesn't disclose whether the tool is read-only, pagination limits, authorization needs, or what happens if rr_id doesn't exist. The behavior is implied but incomplete.

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 a single sentence, front-loading the primary action (List ready replies) and the exception case (or one item if rr_id is set). No extraneous text.

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?

Given the 0% schema coverage, two optional parameters, and no annotations, the description is insufficient. It doesn't explain the return structure (despite output schema existing), parameter behavior, or common patterns for effective use.

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 0%, so the description must compensate. It only mentions rr_id's filtering effect in passing without explaining what group_id does, valid formats, or how the two parameters interact. The description adds minimal value over the raw schema parameter names.

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 lists ready replies and can optionally return a single item when rr_id is set. It distinguishes the listing behavior from sibling tools like workers_readyreply_upsert and workers_readyreply_delete which perform different operations.

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?

There is no guidance on when to use this tool versus alternatives like using rr_id vs no rr_id, or how it relates to other ready reply tools. No context is given about typical use cases or prerequisites.

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