Remove Tag Availablility To Group

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

The description reinforces the permanence already indicated by the destructiveHint annotation. It adds emphasis but does not provide new behavioral insights beyond what annotations supply.

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?

The description includes useful API context but has redundant sentences about permanence. It is somewhat concise but the repetition reduces clarity.

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?

No output schema is provided, and the description does not mention what the tool returns on success (e.g., status code). For a destructive tool with four required parameters, more completeness about expected outcomes is needed.

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?

The input schema has 100% description coverage with detailed parameter explanations. The description only lists required parameters, adding no extra semantics beyond the 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?

The description clearly states that the tool removes a Resource Planning Tag's availability to a group, and differentiates from other tag tools by specifying 'to group' and mentioning Resource Planning records. However, the phrase 'permanently delete the specified Resource Planning records' could cause slight confusion about whether it deletes the tag itself.

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 description says 'Use this to permanently delete...' and warns it cannot be undone, providing basic guidance. However, it does not mention when not to use it or suggest alternative tools like the add counterpart.

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