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

readOnlyHint=true already establishes this as a safe read, so the bar is lower. The description adds useful scope detail: it returns only the first message text and excludes replies/comments. It does not cover pagination, auth requirements, or error behavior for a missing ticket id.

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?

Three short sentences, zero filler. The returned-field list comes first, then the scoping exclusion, then the endpoint hint — well front-loaded and every sentence earns its place.

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?

There is no output schema, so the description carries the burden of describing the return value, and it does so concretely (fields plus the first message text only). For a simple single-read tool this is nearly complete; only error/not-found behavior is absent.

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?

With one parameter at 100% schema coverage, the schema already fully documents ticket_id (including provenance from supportbee_list_tickets). The description's 'GET /tickets/{id}' only echoes the single-id shape without adding format or edge-case guidance, so 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/resource pair implicitly ('one ticket') and enumerates the returned fields (subject, requester, labels, assignees, state, first message text). It also distinguishes itself from siblings by noting replies and comments are separate calls, so an agent can tell it apart from get_reply/list_comments without opening schemas.

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 sentence 'Replies and comments are separate calls' routes the agent away from expecting threaded content and implicitly toward get_reply/list_comments/list_replies. It gives clear context but does not explicitly name those alternatives or state when-not-to-use conditions.

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