Add case property

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It only states that it adds an arbitrary name/value pair, without detailing whether existing properties are overwritten, what the return value is, or any side effects or auth requirements.

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 a single, straightforward sentence that gets directly to the point. It contains no filler or redundant information, making it highly concise and easy to parse.

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?

The tool has no annotations and no output schema, so the description needs to cover expected behavior and results. It omits important context such as what happens on duplicate properties, whether the operation is reversible, and what the response contains, leaving an agent with insufficient information for complex decision-making.

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% coverage with clear descriptions for all parameters (name, value, case_id). The description adds minimal extra meaning via 'arbitrary', which is a slight reinforcement but not necessary given the schema already specifies string types and minLength.

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 references TestCase.add_property, indicating this adds a property to a test case. The phrase 'arbitrary name/value pair' clarifies the nature of the property, but it doesn't explicitly distinguish from sibling tools like kiwi_run_add_property or kiwi_execution_add_property.

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 such as kiwi_case_remove_property or kiwi_run_add_property. The usage is implicitly clear from the name, but there are no explicit context cues or exclusions.

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