publish_repo_escalation

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

With no annotations, the description carries the full burden. It says 'publish' (implying a write) and gives the target path, but discloses nothing about permissions, side effects, whether the write is idempotent, or what happens on failure. For a mutation tool with zero annotation coverage this is a significant gap.

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?

A single efficient sentence with the destination front-loaded and no wasted words. It is concise, though the brevity reflects under-specification rather than deliberate economy.

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?

A mutation tool with no annotations, no output schema, and 0% parameter documentation leaves the agent without the permission, return-value, or field-level context needed to call it correctly. The description does not compensate.

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 all four parameters (repo, from, to, body) are undocumented in both the schema and the description. The <repo> placeholder loosely maps to the repo param, but 'from', 'to', and 'body' receive no explanation at all.

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?

Names a specific verb (publish) and resource (escalation bus item) plus the exact destination path wiki/repos/<repo>/bus/escalation/, which distinguishes it from generic publish_bus_item and publish_repo_discovery. It does not explicitly explain the difference from those siblings, but the 'escalation' scope is clear.

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?

No guidance on when to publish an escalation versus the sibling publish_bus_item or publish_repo_discovery, and no prerequisites or conditions are stated. The agent must infer usage purely from the tool name.

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