ecosystem_apply_debate_result

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It reveals constraints (non-empty fields, enum values) and the intended state transition ('advance to debated'). However, it does not describe side effects, authorization requirements, error conditions, or what happens on success/failure. This leaves significant gaps for a write operation.

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 extremely concise—just two sentences. The first sentence states the core purpose, and the second provides critical usage notes. Every phrase adds value; there is no fluff or redundancy. It is well-structured for quick comprehension.

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?

Given the presence of an output schema and full parameter descriptions, the description provides all necessary context: the tool's role in a multi-stage process, required constraints, and enum options. It is sufficiently complete for an agent to understand how and when to invoke this tool.

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%, providing baseline descriptions for all 6 parameters. The description adds value by clarifying operational constraints: at least one of risks_md, learnings_md, integration_md must be non-empty, and integration_recommendation is an enum with specific values. This supplements the schema beyond mere descriptions.

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 clearly states the tool's purpose: 'Stage 2 writeback — submit debate conclusion to advance to debated.' It uses a specific verb ('submit') and resource ('debate conclusion'), and implies a state transition. This distinguishes it from sibling tools like ecosystem_apply_architecture_md, which have different purposes.

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 explicitly provides a usage constraint: 'At least one of risks_md / learnings_md / integration_md must be non-empty.' It also notes the enum values for integration_recommendation. However, it does not give guidance on when to use this tool over alternatives like other ecosystem_apply_* tools, missing an opportunity for stronger differentiation.

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