Get Transaction Rules

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

Beyond the readOnlyHint annotation, the description explains paging behavior ('Follow next_offset until null'), local paging semantics, page vs total counts, and the difference between compact and verbose results. This is substantial behavioral detail that an agent cannot infer from annotations alone.

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 dense but every sentence earns its place: purpose first, then parameter details, then paging behavior, then output formatting differences. There is no filler or repetition of schema defaults.

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 an output schema present, the description need not restate return structure. It covers the key operational details an agent needs: paging loop, count semantics, local paging caveat, compact field omission rules, and verbose mode. This is complete for a read-only paginated list tool.

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 0%, so the description carries the full burden for parameters. It explains limit's range and default, offset's zero-based meaning, and verbose's effect on returned objects. All three parameters are given meaningful semantics beyond the bare 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: 'Read a page of automation rules in priority order, without modifying them.' This clearly distinguishes the tool from transaction, budget, and account sibling tools, and the read-only scope is explicit.

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 gives clear context for when to use the tool: whenever a page of automation rules is needed, with no mutation. It does not explicitly name alternatives or state when not to use it, but the purpose is unambiguous and no other sibling targets automation rules.

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