Get Resolutions

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

The annotations already declare 'readOnlyHint: true', so the description carries low burden. It adds minimal behavioral context beyond stating the tool retrieves all resolutions for closing issues. It does not describe return format, ordering, or any side effects, but these are not critical given the annotations.

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 sentence with no wasted words. It front-loads the action and resource, making it clear and efficient.

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 no parameters and an output schema, the description is sufficiently complete. It explains what the tool retrieves and in what context (Yandex Tracker, for closing issues). It might be improved by noting the purpose of resolutions, but it is adequate.

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?

There are no parameters, so the input schema coverage is 100% trivially. The description does not need to explain parameters, and the baseline for 0 parameters is 4. The description adds no further parameter info, which is acceptable.

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 uses a specific verb 'Get' and identifies the resource 'resolutions' with a clear context: 'available in Yandex Tracker that can be used when closing issues'. This distinguishes it from sibling tools like 'get_statuses' or 'get_priorities', which are similar but for different entities.

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 implies the tool is for fetching resolutions when closing issues, but it does not explicitly state when to use it over alternatives or when not to use it. Since siblings are also entity-retrieval tools, some explicit guidance would improve clarity, but the context is moderately clear.

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