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

Annotations already establish read-only, idempotent, and non-destructive behavior. The description adds value beyond annotations by disclosing the presence of two distinct URLs with different sharing rules: 'app_url is the INTERNAL deep link... never hand it to the person who opened the ticket' and 'public_url is the PUBLIC ticket page... safe to share.' This is meaningful behavioral context.

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?

The description is three sentences, each focused: first states purpose, second gives alternative tool, third explains the two links. No fluff or repetition. It is front-loaded with the most critical information and maintains high information density.

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?

Given the tool's simplicity (one parameter, no output schema), the description covers the essential aspects: what data it reads (submitter, widget, when), and the two return links with sharing guidance. It doesn't mention return format or error cases, but these are not required given the straightforward nature and annotations.

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%; the description does not mention the pk parameter or its format. Although the schema describes pk as 'The id of the ticketsubmission,' the description fails to compensate for the lack of coverage. The parameter is simple, but the description provides no explicit guidance beyond the tool's purpose.

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?

The description clearly states the tool's function: 'Read the intake metadata of a ticket: who opened it (submitter), which widget, when.' It uses a specific verb (read) and resource (ticket submission), and explicitly distinguishes from retrieve_tasks by noting 'A ticket is a Task; use retrieve_tasks for the task detail.' This differentiates it from sibling tools.

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 description provides explicit guidance on when to use this tool versus alternatives: 'use retrieve_tasks for the task detail and the task tools to triage.' It also gives context about the two links and how to share them appropriately, adding practical usage instructions.

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