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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the description only adds the cost note "3 MESH/call." It does not explain what the routine mutates, what permissions or external access are required, or what side effects occur across its multi-step sequence.

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 run-on sequence filled with non-actionable modifiers such as "adjacent" and "compounding in one direction." The useful cost note is buried at the end, and the core purpose is not front-loaded.

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 complex multi-step routine with a nested object payload and no output schema, the description leaves major gaps: it does not clarify what the input payload should contain, what each routine step changes, or what result the agent should expect.

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 100%, and the schema explains that the single `input` object is a capability-specific payload with examples. The description adds no further meaning about the payload or its nested structure, so the baseline of 3 applies.

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 largely restates the tool name and title with buzzwords like "Collaborative, adjacent, actionable, executable routine," then lists opaque steps ("upgrade in place," "split access," "align to the yellow-pill new look"). It never states a clear verb-plus-resource outcome that distinguishes this tool from siblings such as quiet-query or mesh_post.

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?

It implies a sequence including "Quiet Query" but gives no explicit when-to-use context, prerequisites, or alternatives among the many sibling tools. The routine ordering is the only usage signal, and it is not enough to route an agent correctly.

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