addBdd

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

No annotations provided, so description carries full burden. Discloses creation of test case with specific template_id and custom field population, and required content format. Lacks details on permissions or side effects, but for a simple creation tool it is adequate.

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?

Two sentences: first states purpose, second lists required parameters with needed format. No redundant or extra information. Efficiently front-loaded.

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 simple parameters (2 required, no nesting, no output schema), description fully covers what an agent needs: what the tool does, what parameters are, and their format. No gaps.

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%, but description adds meaning: clarifies that featureContent must be raw Gherkin text with specific keywords, and sectionId is TestRail Section ID. Provides required format and context beyond 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?

Description clearly states verb (imports/uploads) and resource (Gherkin BDD scenario into TestRail section), creating a test case with BDD template. Distinguishes from sibling addCase by specifying BDD-specific behavior.

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?

Specifies required parameters and format for featureContent (including Feature:, Scenario:, Given/When/Then). Implicitly indicates use for BDD scenarios, but does not explicitly contrast with addCase for non-BDD cases. Slightly lacking in 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.