pmg_who_object_delete

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

No annotations provided, so description carries full burden. It discloses irreversibility, dry-run default, mutation type (MEDIUM), and response format. Fully transparent about behavior.

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 key info front-loaded: mutation type, dry-run, irreversibility, alternative, and response format. No unnecessary 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 mutation nature and dry-run complexity, description covers all critical aspects: source of IDs, alternative tool, execution with confirm, return format. Output schema exists, so return value is documented; description adds clarity.

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 100%, baseline 3. Description adds value by specifying data sources for id_ and ogroup, and explaining the confirm parameter's effect. Enhances understanding beyond schema.

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?

Cleary states it deletes an object from a PMG RuleDB 'who' object group, with dry-run by default. Differentiates from sibling pmg_who_group_delete explicitly.

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?

Explains when to use (delete object from 'who' group) and when not to (use pmg_who_group_delete for whole group). Also clarifies dry-run behavior and how to execute with confirm=True. Lacks explicit prerequisites but provides good contextual guidance.

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