delete_glue

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

The description implies a destructive action ('Remove') but provides no additional behavioral context such as reversibility, authorization requirements, or side effects. With no annotations, this is insufficient.

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?

Extremely concise: two sentences with no wasted words. The action=GLUE_DELETE is helpful for context. Could be improved by integrating the action into the main sentence.

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?

Lacks output schema, no parameter guidance, and no behavioral context. The description is too sparse to fully inform an agent about correct usage for a tool with three required parameters and a destructive action.

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 0%. The description does not explain the purpose or format of the required parameters (host, domain, reason). The agent must rely solely on the schema titles, which are minimal.

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 action: remove a glue record by host name. It uses a specific verb ('Remove') and resource ('glue record'). However, it does not differentiate from sibling tools like delete_dns_record, though it is distinct among glue-related 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?

No guidance on when to use this tool versus alternatives (e.g., delete_dns_record, delete_dnssec_record). The description only states the action without context on prerequisites or exclusions.

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