Add case attachment

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

No annotations are provided, so the description carries the full burden of disclosing behavioral traits. However, it merely restates the function name and lists the input fields ('filename plus base64 content'), without mentioning side effects, permissions, file size limits, or error conditions. This is a significant transparency 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 extremely concise at one sentence, with no filler words. However, the first part 'TestCase.add_attachment' simply echoes the tool name, which is somewhat redundant, and the rest is limited to parameter listing. It is brief but not inefficiently wordy.

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 tool has simple parameters and no output schema, a short description might suffice. However, with no annotations and no behavioral context, the description is incomplete: it does not explain what the operation does beyond 'add', any consequences, or how it fits with related attachment tools. The agent is left without enough information to confidently use this tool in 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?

The input schema covers all three parameters with clear descriptions (case_id, filename, b64content) at 100% coverage, so the baseline is 3. The description's mention of 'filename plus base64 content' adds no new meaning beyond the schema's existing field descriptions, making it redundant but harmless.

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 'TestCase.add_attachment: filename plus base64 content' clearly indicates that this tool adds an attachment to a test case. It distinguishes itself from sibling attachment tools for plan, run, and execution by explicitly referencing 'TestCase', and the title 'Add case attachment' reinforces the action and target.

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 provides no guidance on when to use this tool versus the many sibling attachment tools (e.g., kiwi_plan_add_attachment, kiwi_run_add_attachment, kiwi_execution_add_attachment). It does not mention any exclusions, prerequisites, or alternative scenarios, leaving the agent to infer based solely on the tool name.

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