execute_transition

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the write/destructive nature is covered. The description adds one genuinely new behavioral fact beyond annotations: 'Изменяет данные в Трекере; подтвердите целевой переход с пользователем' establishes a human-confirmation requirement. It says nothing about irreversible state changes, permissions, or whether 'fields' accompanies the transition.

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, mutation fact and confirmation guardrail front-loaded, no filler. It is appropriately sized; the only cost is that the brevity comes at the expense of the missing detail noted above.

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 destructive mutation on an issue tracker, an agent still lacks where transition_id comes from (list_transitions), whether the transition may require fields, and what permissions are needed. An output schema exists, so return values need not be described, but the preconditions and parameter sourcing are not covered.

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% across 3 parameters, so the schema provides no meaning for issue_id, transition_id, or fields, and the description does not compensate. 'Целевой переход' loosely maps to transition_id and confirms it is the destination status, but issue_id and especially the opaque 'fields' object are left entirely unexplained.

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 gives a specific verb + resource: 'Выполнить переход статуса задачи' (execute an issue status transition). An agent knows exactly what mutation is performed. It does not distinguish itself from the sibling list_transitions, which is the natural companion tool for obtaining the transition to execute.

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?

Usage is only implied: it instructs the agent to confirm the target transition with the user before acting, which is a useful workflow guardrail. However, it never states when to prefer this over list_transitions (to discover valid transitions) or update_issue (to change fields without a status change). No alternatives or exclusions are named.

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