pmg_who_object_delete

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

Discloses it is a mutation (MUTATION), describes the dry-run behavior, and the need for confirm. No annotations exist, so the description fully carries the burden. Also notes the consistent path /objects/{id} regardless of type.

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?

Concise, informative, and well-structured. Uses line breaks for readability. Every sentence adds value without redundancy.

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 presence of an output schema (context signals indicate has output schema=true), the description adequately covers the action, parameters, prerequisites, and path. No need to explain return values.

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 25% (only proximo_target has description). The description adds meaning for ogroup and id_ by specifying their sources (ogroup from pmg_who_groups_list, id_ from pmg_who_group_objects). This compensates for low coverage but does not cover all parameters.

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 verb 'delete' and the resource 'object from a PMG RuleDB 'who' object group'. It distinguishes from sibling tools like pmg_who_object_add or pmg_who_object_update by specifying the operation type and path.

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 context: dry-run by default, need confirm=True to execute, and config requirement. However, it does not explicitly mention when not to use this tool compared to other delete tools for different groups (e.g., pmg_what_object_delete).

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