create_reliance

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

With no annotations, the description carries full burden. It discloses that the edge enters draft, runs LLM semantic validation, and carries no credit until confirmed. This provides important behavioral context, though it could mention idempotency or error conditions.

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 concise paragraphs with clear front-loading of purpose. Structured as bullet points in text, no redundant sentences. Every sentence adds value.

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?

Covers purpose, modes, scope, lifecycle, and credit semantics. With output schema present, return values are not needed. Could be more complete by discussing failure modes or idempotency, but it's sufficient for a complex 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?

With 86% schema coverage, baseline is 3. The description adds value by explaining conditional parameters (`source_objective_id`, `source_control_id`) in the context of modes, clarifying when each is required.

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?

Clearly states 'Declare a cross-model dependency' and explains two modes, distinguishing it from sibling tools like `link_dependency` or `declare_foundation`. The verb 'create' and resource 'reliance' are specific and unambiguous.

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?

Provides detailed guidance on when to use each mode (delegated vs relied_upon) with specific parameter requirements. Mentions workspace-scoping and confirmation via `confirm_reliance`. However, does not explicitly contrast with alternative tools or state when not to use.

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