get_custom_psa_ticket_detail

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

Discloses use of POST due to credentials in body, but annotations indicate readOnlyHint=false, contradicting the apparent read-only intent of 'retrieve'. No disclosure of side effects or response format.

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?

Single sentence with a brief technical note, concise and front-loaded, but could include structured use cases.

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?

Lacks description of output (what 'detailed information' includes), no mention of response format, and no guidance on handling credentials despite schema coverage.

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 covers all three parameters with descriptions, and the tool description adds no additional meaning beyond schema, yielding baseline 3.

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 specifies the action 'Retrieve detailed information' and the resource 'specific Custom PSA ticket', clearly distinguishing it from the sibling list_custom_psa_tickets which lists tickets.

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?

No guidance on when to use this tool vs alternatives, no prerequisites or when-not-to-use conditions mentioned. The note about POST method is technical, not usage guidance.

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