pmg_what_object_delete

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

Discloses mutation type (MEDIUM), irreversibility, dry-run behavior, and the confirm parameter effect. No annotations provided, so description carries the burden and does well. Could mention error handling but overall strong.

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 covering purpose, irreversibility/alternatives, and execution details. Efficiently front-loaded with key information, no wasted words.

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 an output schema exists, the description adequately explains the mutation and dry-run. It could mention error scenarios or permissions, but overall sufficiently complete for a delete 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 100% schema coverage, the description adds value by explaining the source of id_ and ogroup, the dry-run vs execution semantics of confirm, and the purpose of proximo_target. This goes beyond the schema descriptions.

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 ('delete an object from a PMG RuleDB 'what' object group') and highlights the dry-run default, distinguishing it from sibling tools like pmg_what_group_delete.

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 clear guidance: id_ comes from pmg_what_group_objects, and explicitly mentions the alternative tool for deleting the whole group. Lacks explicit 'when not to use' but the alternative is clear.

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