coding_prioritize_backlog

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

Annotations already convey destructiveHint=true and readOnlyHint=false. The description adds the routing/scope behavior ('Routes through the platform's domain-agent dispatcher under your JWT, tenant, and company scope'), which is useful context. It does not disclose what effects the action has or whether it is asynchronous.

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 short, front-loaded, and free of filler. The action statement comes first, followed by routing context and parameter definitions. It earns each sentence, though it is thin.

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 marked destructive with no explanation of what the underlying action does, the description is incomplete. It does not describe when to invoke prioritize_backlog, what the structured inputs should contain, or what side effects to expect. The output schema and annotations help, but the core semantics are missing.

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%, so the description must compensate. It does define both parameters: message as 'Free-text objective' and inputs as 'Optional JSON string of structured inputs.' This adds basic meaning, but it lacks detail about what structured inputs are valid for the prioritize_backlog action.

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 states a specific action ('Run the coding domain agent action `prioritize_backlog`') and adds routing context that distinguishes it as a domain-agent wrapper. However, it never explains what 'prioritize_backlog' actually accomplishes, relying heavily on the tool name for meaning.

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 provides no guidance on when to use this tool versus alternatives such as coding_process_single_ticket, coding_generate_tickets, or dispatch_domain_agent. It only mentions routing under JWT/tenant/company scope, which is contextual but not usage direction.

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