Create Test Plan

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

Annotations indicate readOnlyHint=false and destructiveHint=false, which are consistent with creating a non-destructive entity. The description adds behavioral context by explaining that the tool can create a plan using explicit IDs, an AQL filter, or both. This goes beyond the annotations without contradiction.

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 three sentences, front-loaded with the primary action and resource. It efficiently covers purpose and methods without unnecessary words.

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's simplicity and the existence of an output schema, the description provides sufficient context: it identifies required parameter (name), explains optional parameters, and outlines the two content selection strategies. No gaps remain.

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 100%, so the baseline is 3. The description adds value by explaining the dual approaches (test_case_ids and aql_filter) and their combined use, enhancing understanding beyond the schema. Output_format is well-described in 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 the verb 'Create' and the resource 'Test Plan in Allure TestOps'. It differentiates from siblings like 'manage_test_plan_content' and 'update_test_plan' by focusing on creation, and explains the two primary methods for defining content (test_case_ids and aql_filter).

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 explains when to use the tool (to create a new test plan) and outlines the two content selection methods. It does not explicitly state when not to use it or name alternatives, but the context implies it is for creation only, which is clear from the purpose.

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