Remove case property

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It merely states the operation and a filter, but does not mention that removal is destructive, whether it requires permissions, what happens if multiple properties match, or if the operation is reversible. This is a significant gap for a mutation tool.

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 very brief, but the first clause 'TestCase.remove_property' largely repeats the tool name and title, adding no new information. The second clause provides some filter guidance, but the overall structure could be improved by eliminating redundancy and including essential details.

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?

For a destructive operation with no annotations and no output schema, the description is incomplete. It fails to mention property_id, does not clarify how the filtering works when multiple properties exist, and does not describe what the tool returns or any side effects. The schema covers parameter names but not usage context.

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 descriptions cover 100% of parameters, but the description adds 'Filter by case_id and/or name,' which omits property_id and could mislead an agent into thinking only those two parameters are relevant. This introduces ambiguity rather than adding clear semantic value 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 title and description clearly indicate this tool removes a property from a test case. The phrase 'TestCase.remove_property' and 'Filter by case_id and/or name' give a clear sense of the operation, but the description omits the property_id parameter, which is part of the schema and could be the primary removal key.

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 about when to use this tool versus alternatives like kiwi_case_add_property or removal tools for tags/components. The only hint is 'Filter by case_id and/or name,' which suggests some selection logic but does not explain prerequisites or exclusions.

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