ecosystem_link_integration_task

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

No annotations provided, so full burden is on description. It only states the action (linking) but omits behavioral traits like idempotency, overwrite behavior, permissions, or error handling. Minimal disclosure for a mutation tool.

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?

Very concise single sentence, front-loaded with key action. However, it is extremely terse and could benefit from slight expansion without losing efficiency.

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 simple tool with an output schema, the description lacks context about its role in the pipeline (Stage 3), prerequisites, or outcome. Not enough for an agent to decide when to invoke it.

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 coverage is 100%, and existing parameter descriptions are clear ('Task id returned by...', 'Target deep_review row id.'). The description adds no extra meaning, so baseline 3 is appropriate.

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 'link integration task id back to review row', which is a specific verb+resource that clarifies the tool's purpose. However, it does not differentiate from sibling tools like 'ecosystem_link_debate_meeting', but the action is distinct enough.

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 use this tool versus alternatives. The description mentions 'Stage 3 helper' implying a pipeline context but provides no explicit when/when-not or alternative tools.

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