roadmap_link_task

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies a write operation but does not say whether linking requires the roadmap outcome to pre-exist, whether it is idempotent, whether it overwrites a prior link, whether one task can be linked to multiple outcomes, or what permissions are needed. 'One existing canonical task' hints at singularity and task state, but that is thin for an unannotated 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?

A single front-loaded sentence with no filler; the verb and both operands come first. It is concise and readable, though the extreme brevity is also the source of the semantic gaps noted elsewhere.

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 an unannotated link/mutation tool with two required parameters, 0% schema description coverage, and no output schema, the description is too sparse. An agent cannot infer valid ID forms, failure modes (missing task, missing outcome, already-linked), or the effect of the operation from this text alone.

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% and neither property has a description, so the schema contributes nothing. The description mentions 'canonical task' (hinting task_id must be a canonical task identifier) but says nothing about roadmap_id's format or whether it refers to a roadmap outcome rather than the roadmap itself, leaving both parameters under-specified.

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 verb (Link) and two resources (an existing canonical task, a Roadmap outcome), so an agent knows this is a linking/mutation operation rather than a creation or listing one. It implicitly distinguishes itself from roadmap_add and the needfix link siblings, but it never names an alternative or explicitly contrasts its scope with them.

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?

There is no statement of when to link versus when to create, migrate, or use the needfix link tool. The only usable hints are the adjectives 'existing' and 'canonical', which imply the task must already exist and be canonical, but there are no prerequisites, exclusions, or named alternatives.

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