manage_constraints

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

No annotations are provided, so the description carries the full burden. It reveals the dual read/destructive-mode design, but says nothing about deletion being irreversible, whether it requires confirmation permissions, what happens to dependent features, or what an invalid index does. For a tool whose 'delete' path mutates the model, this is a real gap.

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 elements: a one-line purpose sentence followed by a compact Args block. Front-loaded, no filler, and every line carries information about behavior or parameters.

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?

An output schema exists, so return values are covered elsewhere, and all three parameters get some explanation. But for a tool with a destructive branch and zero annotations, the absence of any warning about irreversible deletion or index validity leaves a meaningful hole for safe invocation.

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 coverage is only 33% (only 'instance' is documented in the schema), but the description compensates by enumerating the accepted values of 'action' ("list" or "delete") and explaining that 'index' is a constraint index obtained from list. That covers the two undocumented parameters meaningfully, though defaults (action='list', index=0) go unmentioned.

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 names a specific verb pair and resource: 'List the active assembly's constraints, or delete one.' That tells an agent exactly what the tool operates on. It does not explicitly distinguish itself from the sibling 'constrain' (presumably constraint creation), leaving the create-vs-manage split to inference.

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 'list' then 'index from list' sequencing implies the correct two-step workflow for deletion, which is useful guidance. However, there is no statement about when to use this versus 'constrain', no prerequisites, and no note that delete is only meaningful with an index obtained from a prior list.

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