mutate_section

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false. The description adds no further behavioral details beyond restating the action mechanism, such as error cases, partial update behavior, or permission requirements. It does not contradict the annotations, but it contributes minimal additional transparency.

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, front-loaded sentence that immediately names the resource and scope. Every word earns its place; there is no filler or redundancy.

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?

Despite the dual-action complexity (oneOf two payload shapes), the schema and description together provide sufficient guidance for an agent to select and invoke the tool correctly. The absence of an output schema means return-value documentation is unnecessary. Minor gap: prerequisite context like suite_id requirements is embedded in the schema but not reiterated in the description, though that is acceptable given schema richness.

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 schema has 100% description coverage, with each property (name, action, project_id, suite_id, parent_id, section_id, description) already documented. The description's instruction to set payload.action duplicates schema constraints and adds no new semantic meaning. Baseline 3 is appropriate because the schema does the heavy lifting.

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 tool's purpose: 'Create a new section or update an existing section in TestRail.' It specifies the resource (sections) and the action (create/update), which distinguishes it from sibling tools focused on suites, runs, or queries.

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 the operation selection mechanism via payload.action, implying that this tool handles both creating and updating sections. However, it does not explicitly contrast with alternatives like get_sections or other mutation tools, so there is no strong 'when not to use' guidance.

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