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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower; the description adds real value by enumerating what is returned (code, inputs, authid, status, verification status) and by flagging response size as a concern with a mitigation. It stops short of describing pagination or the cost of pulling full code payloads.

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?

Two short sentences, zero filler, with the core purpose front-loaded and the optimization hint trailing. Every clause carries information the agent can act on.

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 four simple flat parameters, full schema coverage, and no output schema, the description covers purpose, invocation contract, and returned fields. It could be slightly more complete about whether results are paginated or how many versions are typically returned, but an agent has enough to call it correctly.

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%, so the schema already documents orgId, fields, filter, and identifier. The description reinforces the filter/identifier contract and the fields trimming tip but adds no syntax or format detail beyond what the schema states; baseline 3 applies.

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 states a specific verb and resource ('List all versions of an action or trigger') and even discloses the underlying API filter and identifier form. It is clearly distinguishable from siblings like list_actions_and_triggers or list_auth_versions by resource, though it never names an alternative explicitly.

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?

Usage is only implied: the parenthetical shows the required filter/identifier pairing needed to invoke it correctly, and the final sentence advises using fields for small responses. There is no explicit statement of when to choose this over list_auth_versions or list_actions_and_triggers, nor any prerequisite or exclusion guidance.

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