tdx-ticket-get

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

With no annotations provided, the description carries full burden for behavioral disclosure but only states the action without details on permissions, rate limits, error handling, or response format. It doesn't contradict annotations (none exist), but fails to add meaningful context beyond the basic operation, leaving the agent with insufficient information about how the tool behaves in practice.

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 a single, efficient sentence with zero wasted words—'Get a TDX ticket by ID' directly communicates the core functionality without unnecessary elaboration. It's appropriately sized for a simple retrieval tool and front-loads the essential information.

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 (2 parameters, 100% schema coverage) but lack of annotations and output schema, the description is incomplete. It doesn't address what the tool returns (e.g., ticket fields, error cases) or behavioral aspects like authentication needs, leaving gaps that could hinder effective agent usage despite the straightforward operation.

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 100%, so parameters are fully documented in the schema. The description doesn't add any semantic information beyond what the schema provides (e.g., explaining ticket ID format or app ID usage), but meets the baseline since the schema handles parameter documentation adequately.

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 action ('Get') and resource ('a TDX ticket by ID'), making the tool's purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'tdx-ticket-search' or 'tdx-ticket-feed-get', but the specificity of retrieving by ID provides some implicit distinction.

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 no guidance on when to use this tool versus alternatives like 'tdx-ticket-search' for broader queries or 'tdx-ticket-feed-get' for feed-related data. It lacks context about prerequisites or typical use cases, offering only the basic operation without comparative information.

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