gorelo_get_ticket_approval

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

readOnlyHint=true already declares the safety profile, so the description's job is lighter. It does add useful context that this endpoint is the sole home of approval status and that conversations are intentionally lean, but says nothing about response shape, permissions, or whether approver data can be paginated or partial.

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 short sentences with the core action front-loaded; the second sentence earns its place by explaining why approval status is not available elsewhere. Slightly indirect phrasing ('This is where approval status lives') rather than a crisp statement of scope keeps it off a 5.

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 two-required-parameter read tool with full schema coverage and no output schema, the description covers what is retrieved (the approval plus its approvers) and why it exists as a separate endpoint. The only gap is the shape of the returned approval object, which matters somewhat given there is no output schema.

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 both ticketId and approvalId are already documented, including the note that approvalId comes from the conversations endpoint. The description adds no additional syntax, format, or sourcing guidance beyond that, so the 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 ('Gets') and a precisely scoped resource ('a single approval on a ticket, with its approvers'), which separates it from the plural/list siblings like gorelo_list_ticket_conversations. It doesn't name the parallel task-level tool (gorelo_get_project_task_approval) that an agent might confuse it with, so differentiation is strong but not complete.

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 second sentence implies usage — look here for approval status because the conversations list deliberately omits it — which is a genuine routing hint. However, it never states an explicit 'use this when...' condition or names a specific alternative sibling tool to prefer.

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