Delimit Agent Link

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

Annotations already indicate this is not read-only and not destructive. The description adds value by stating the exact side effect: 'writes the link via ai.agent_dispatch.link_ledger_item.' This tells the agent the operation mutates state and reveals the underlying write path, which is useful behavioral context beyond the annotations.

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 longer than the bare minimum but every section earns its place: purpose, when to use, when not to use, sibling contrast, and side effects. It is well-structured and front-loaded with the core purpose, though it is slightly more verbose than strictly necessary.

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 simple two-parameter tool with an output schema and annotations, the description covers the essential context completely: what the link does, when to create it, when to avoid it, how it differs from related tools, and what side effect it performs. Nothing critical is missing.

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 both parameters have descriptive names plus format hints (AGT-xxx, LED-xxx/STR-xxx). The description itself does not add parameter-level detail, but the schema already carries that burden, so a baseline score of 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 opens with a specific verb and resource: 'Link an agent task to a ledger item' and explains the purpose (dashboard relationship). It also distinguishes itself from delimit_agent_dispatch and delimit_ledger_link, so an agent can quickly tell what this tool does versus its most similar siblings.

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 'When to use' section gives a clear precondition: after delimit_agent_dispatch creates a task and the dashboard should show the ledger item. The 'When NOT to use' section explicitly names the alternative tools for dispatching and completing tasks, and the sibling contrast further disambiguates from delimit_ledger_link.

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