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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered; the description adds real value beyond that by disclosing sort order, the exclusion of internal notes, the per-status counts, and the exact fields returned. It does not discuss pagination limits beyond 'limit', but the tool has no cursor parameter, so there is little more to say.

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?

Front-loaded with purpose and routing, then filters, then return shape. Dense but each clause carries information; the 'Returns:' block does real work since no output schema exists, though the status/limit restatement duplicates the schema.

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, the description compensates well by enumerating ticket fields and per-status counts. The only gap is the multi-company `company` parameter, left entirely to the schema, which is acceptable but slightly incomplete for a tool whose resource is company-scoped.

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 schema already defines all three parameters. The description restates status semantics ('active = open + pending, the default') and the limit range but never mentions the company parameter, so it adds no meaning beyond the 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?

States a specific resource (the company's support requests to the BerthTime team), its sort order (most recent activity first), and a scope boundary (internal staff notes never included). It also names the counter-tool (create_ticket) for the opposite operation, so the agent can distinguish listing from creating without consulting schemas.

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?

Explicitly says to use it to check the status of a request and routes ticket creation to create_ticket. No guidance is given for viewing a single ticket's full thread or history, which leaves one plausible alternative path unaddressed.

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