get_ticket

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered, and the description adds real value by listing the sections returned in the indexed text. It says nothing about behavior when the key is unknown, permission requirements, or result size, which matter for a full-text 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?

A single front-loaded sentence with the payload contents enumerated; nothing is wasted. It is efficient but so terse that the missing parameter explanation is not compensated elsewhere.

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, but with two required, zero-coverage parameters the definition leaves an agent unable to determine what "source" accepts. For a lookup tool whose correctness depends entirely on those inputs, this is a significant gap.

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 carry the burden, yet it explains neither parameter. "source" in particular is opaque (which tracker/system?) and no key format is given, leaving both required parameters semantically undocumented.

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?

"Full indexed text of one ticket" states a specific resource and scope, and the enumeration of description, comments, links and time spent tells the agent exactly what content comes back. It does not name or contrast itself with the sibling similar_tickets, so the distinction has to be inferred.

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 when-to-use or when-not-to-use guidance and no mention of the alternatives (similar_tickets, precedents_for, list_sources). An agent must guess that this is the single-ticket retrieval path versus the related-ticket paths from the sibling names alone.

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