get_my_jira_tickets

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

With no annotations, the description carries the full burden. It usefully discloses the non-obvious association semantics (assigned, reported, or mentioned) and implies an authenticated read via 'authenticated user', but says nothing about pagination, result volume, or return shape.

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?

Two tight sentences; the scope-defining clause is front-loaded and the filtering capabilities follow. The second sentence largely restates what the schema already conveys, so it earns slightly less than full marks.

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 tool with zero required parameters, 100% schema coverage, and no output schema, the description covers the essentials: what is retrieved and how results are scoped. Only the absence of pagination/return-volume context keeps it from being fully complete.

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 coverage is 100%, so the schema already fully documents all four parameters including enum values and defaults. The description only paraphrases three of them (status, project, username) and omits max_results, adding no meaning beyond the schema. Baseline 3 applies.

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 (Retrieve) and resource (Jira tickets) with the key scoping qualifier that they belong to the authenticated user, further clarified as assigned, reported, or mentioned. This user-scoping distinguishes it reasonably well from the generic search_jira_tickets sibling, though no sibling is named explicitly.

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 user-centric scope implies when to use it (when you want the caller's own tickets rather than arbitrary search results), but there is no explicit 'use X instead of Y' guidance and no stated conditions or exclusions. Usage is left to inference.

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