get_gtt_rule_list

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

The description adds pagination behavior, which is useful beyond the openWorldHint annotation. However, it does not mention authentication, rate limits, or output structure, so it provides moderate rather than rich behavioral context.

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 concise sentence that front-loads the primary action ('List GTT rules') and includes the key qualifier (filtered by status) and a behavioral note (paginated results). Every word contributes value with zero redundancy.

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 simple list tool with all parameters documented, the description is adequate: it covers the core purpose and pagination. It does not detail the return structure, but the absence of an output schema is partially mitigated by the clear 'List GTT rules' phrasing and the pagination note.

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 100% with each parameter described. The description only ties 'filtered by status' and 'paginated results' to existing schema concepts, adding no new semantic meaning beyond what the schema already provides.

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 GTT rules with status filtering, using a specific verb and resource. It distinguishes from mutation siblings (create/modify/cancel) but does not explicitly compare to get_gtt_rule_details, so it loses a point for not ensuring sibling differentiation.

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?

No guidance is provided on when to use this tool versus alternatives like get_gtt_rule_details. The description only states what it does, not when it should be chosen over other GTT tools, leaving the agent to infer appropriate usage.

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