get_my_tickets

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

With no annotations provided, the description carries the full behavioral burden. It does disclose that results are scoped to the authenticated user and that workspace falls back to a configured/primary default, but it never confirms read-only semantics, pagination, ordering, or rate behavior for what is presumably a bulk fetch.

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 summary sentence followed by a compact args block; the purpose is front-loaded and every line carries meaning. No filler or restated boilerplate.

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?

An output schema exists, so return values need not be described, and both parameters are covered. The remaining gap is that pagination/ordering behavior for a limit-bounded list is unstated, which matters slightly for correct invocation but is not fatal.

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 must compensate, and it does: workspace is explained as an optional slug defaulting to the configured or primary workspace, and limit is described as a maximum count with default 50. That adds real fallback semantics beyond the bare property names, though it omits any pagination or offset interaction.

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 with scope: tickets assigned to the authenticated user in a given workspace. That scope implicitly separates it from siblings like search_tickets or get_ticket, but the description never names an alternative, so differentiation is left to inference.

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 explicit when-to-use or when-not-to-use guidance, and no alternatives (search_tickets, get_ticket) are referenced. The scope phrase 'assigned to the authenticated user' implies when it applies, but an agent must infer the routing decision entirely.

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