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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: no indication of whether results are paginated, how they are ordered, whether all statuses are returned when the filter is omitted, or roughly what the response contains.

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?

It is a single short sentence with no filler, which is appropriate in length. However, the clause 'and replies status' is grammatically muddled and front-loading the filter behavior would have been more useful than the ambiguous addendum.

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 no output schema and a zero-coverage parameter schema, the description needs to explain default behavior, filtering semantics, and result shape for an open-world listing tool. It covers none of these, leaving an agent unable to predict what a call with no arguments returns.

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 burden of explaining the single 'status' parameter — yet it never states that the parameter filters results, nor what happens by default (all tickets?) when it is omitted. The enum values live only in the schema, and the description does not connect them to filtering behavior.

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 names a verb and resource ('List support tickets'), which is better than a bare restatement of the name. But the trailing 'and replies status' muddies the purpose — it is unclear whether this lists tickets, ticket replies, status metadata, or all three, and nothing distinguishes it from siblings such as bridge_open_ticket or bridge_failed_webhooks.

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 guidance on when to use this versus the other bridge_* listing tools, and no stated preconditions (auth, connected account, openWorld requirements). The agent is left to infer usage entirely from the tool name.

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