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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds details not in the annotations: a hard cap of 50 results, newest-first ordering, and that calls are not metered. It does not describe behavior when more than 50 tickets exist (silent truncation) or failure modes.

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?

One dense sentence that front-loads the resource and scope, then the cap and ordering, then the returned fields. No sentence is wasted.

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 and 100% param coverage, the description is more than sufficient for a one-parameter read tool. The only real gap is whether the 50-item cap implies results can be silently truncated, which matters for an agent deciding whether it has seen everything.

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?

There is a single required parameter with 100% schema description coverage, so the schema already fully documents workspace_tag. The phrase "in one workspace" reinforces that the parameter scopes results to a single workspace but adds no syntax or format detail 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 verb and resource ("Lists ... support tickets") along with scope ("this principal's", "in one workspace"), ordering, cap, and the fields returned. An agent can distinguish it from the write sibling submit_support_ticket without opening any schema.

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 read-only framing and "this principal's" scoping make the intended use clear, and "not metered" signals it is cheap to call for status checks. It never names an alternative or states when not to use it, so it stops short of explicit routing guidance.

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