Get Request Resolution

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

No annotations are provided, so the description carries the full burden, and it discloses nothing: not whether it is a read, whether a resolution may be absent (and what that returns), nor any auth or error behavior. 'Get a resolution' gives no behavioral context at all.

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?

It is short, but this is under-specification rather than conciseness — a single four-word fragment that earns none of its brevity by conveying meaning.

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 tool with an undocumented required parameter, no annotations, no output schema, and a crowded sibling namespace, this description is wholly inadequate; an agent has no basis for selecting or correctly invoking it.

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% for the single required parameter request_id, and the description says nothing about it — not whether it refers to the request whose resolution is fetched, nor its format. The description fails to compensate for the schema gap.

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 'Get a resolution' is essentially a restatement of the tool name and title, adding no scope, no verb specificity beyond 'get', and no differentiation from siblings like get_request, get_request_summary, or add_request_resolution. 'Resolution' is never defined, so an agent cannot tell what entity is actually being fetched.

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?

There is no guidance on when to use this tool versus get_request, get_request_summary, list_request_notes, or add_request_resolution. No prerequisites, no conditions, no exclusions.

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