Disconnect Blueprint

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

Annotations already indicate destructive and idempotent behavior. The description adds specific context: it stops syncing via `render.yaml` and does not delete managed resources, clarifying the scope of the destructive action. No contradiction with 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?

Three sentences are relatively concise, but the first sentence ('Disconnect Blueprint') is redundant with the title. The structure is clear: purpose, effect, and API route.

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 one-parameter tool with no output schema, the description provides sufficient context: what it does, what it does not do, and the underlying API call. Could optionally mention idempotency but is adequate.

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?

The single parameter blueprintId has 100% schema coverage with its description. The tool description adds no further meaning beyond the schema, meeting the baseline for high coverage.

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 explicitly states the tool 'Disconnect Blueprint' stops automatic resource syncing, clearly differentiating it from sibling tools like render_list_blueprints, render_update_blueprint, and render_delete_service.

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 description implies usage for stopping syncing but does not explicitly state when to use it versus alternatives. It mentions that it does not delete resources, offering indirect contrast, but lacks clear when-not or alternative guidance.

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