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

The readOnlyHint annotation already indicates this is a safe read operation, so the description does not need to restate that. The description adds the API endpoint, which is mildly helpful, but it does not disclose pagination behavior, response shape, or any other behavioral nuance beyond what annotations and schema already convey.

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 two short sentences with no filler. The core action is front-loaded, and the API reference is appended cleanly without disrupting readability.

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 read-only list operation, the description plus schema and annotations provide enough to select and call the tool: it lists subscriptions, supports optional filters, and the schema documents pagination parameters. The lack of an output schema means return details are somewhat implicit, but 'List subscriptions' sufficiently implies the response contains subscriptions.

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 parameters are fully documented in the input schema. The description's mention of filtering by customer or status aligns with the schema but adds no new semantic detail beyond what the parameter descriptions already provide.

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 names the verb and resource: 'List subscriptions' and adds a useful detail about filtering by customer or status. It is distinct from the sibling orb_get_subscription by being a list operation, but it does not explicitly differentiate itself from any specific sibling.

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 phrase 'optionally filtered by customer or status' implies when the tool is useful, and the 'List' framing suggests use for collections rather than single subscriptions. However, there is no explicit guidance about when to choose this tool over alternatives like orb_get_subscription or when not to use it.

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