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

readOnlyHint=true already tells the agent this is a safe read. The description adds modest context: it is a Control API operation scoped to a single app. It says nothing about pagination, result limits, or what happens on an invalid app_id, so it clears the lowered annotation-aware bar only modestly.

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 sentences, zero waste. The core purpose and its disambiguating detail are front-loaded, and the API path is appended rather than padding the opening.

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 one required parameter, no annotations beyond readOnly, and no output schema, the description is nearly sufficient: the enumeration of rule types gives the agent a sense of what comes back. It would be complete with a note on result volume or pagination.

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%, and the single app_id parameter is already documented in the schema with the same cross-reference ('from ably_list_apps'). The description adds no parameter syntax or format detail beyond the schema, so 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 the integration rules ... configured for an app') and immediately disambiguates the vague term 'rules' by enumerating what they are (webhooks, AWS Lambda/SQS/Kinesis, Kafka, Pulsar). It does not explicitly contrast itself with sibling list tools like ably_list_namespaces or ably_list_queues, so it falls just short of the top band.

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 when-to-use guidance, no prerequisites, and no mention of alternatives among the many sibling list/get tools. The Control API path is a technical detail, not usage guidance, so an agent gets no routing help.

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