remove_tag_property

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

The description is too brief, stating only 'Remove a property from a tag' without disclosing behavioral traits such as whether the removal is destructive, if it requires specific permissions, or any side effects. No annotations are present, so the description carries the full burden, which it fails to meet.

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 is extremely concise (one sentence), but it sacrifices completeness. While no unnecessary words are present, the brevity fails to provide adequate information, earning a middle score.

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 lack of annotations and output schema, the description should provide more context about the tool's behavior and constraints. It does not mention whether the tag or property must exist, if the operation is reversible, or what happens after removal. The description is insufficient for a simple but potentially destructive 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?

Schema description coverage is 0%, and the description adds no meaning beyond the schema definition. For example, 'property_id_or_name' could be clarified to indicate whether it accepts an ID or name, or how it resolves conflicts. The description provides no such extra context.

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) and the object (property from a tag). It distinguishes from sibling tools like 'add_tag_property' and 'remove_tag_extends' by specifying the exact operation, but does not elaborate on what constitutes a property on a tag.

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 is provided on when to use this tool versus alternatives like 'remove_property'. The description does not mention prerequisites, conditions, or typical use cases, leaving the agent to infer usage solely from the tool name.

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