roadmap_block

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

No annotations provided, so description carries full burden. It describes the action and the effect in roadmap_view, but does not mention idempotency, error handling, or what happens if the dependency already exists. Minimal transparency beyond the core action.

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?

Two sentences include purpose, usage guidance, and view context. No wasted words, front-loaded with key action.

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?

Description is sufficient for a simple dependency creation tool with two required parameters. References parent_id for clarity and mentions output in roadmap_view. Does not discuss error cases or return values, but output schema likely covers that.

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 titles are minimal ('Blocked Id', 'Blocked By Id'), and description adds the relational meaning: 'node blocked_id is blocked by blocked_by_id' and clarifies it's a dependency edge. With 0% schema description coverage, this adds significant value.

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 verb 'Record' and the resource 'DEPENDENCY edge', and distinguishes it from sibling tool behavior by explicitly saying not to overload parent_id.

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?

Explicitly tells when to use this tool ('for real dependencies instead of overloading parent_id') and provides context on how it surfaces in roadmap_view.

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