testmo_record_results_bulk

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

With no annotations, the description carries the burden of disclosing behavioral traits. It clearly discloses the critical all-or-nothing validation behavior: an invalid item rejects the whole batch. It also mentions the batch size limit (1-100). This adds significant context beyond the schema, though it does not cover authentication or return format.

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, front-loaded with the primary purpose and followed by essential constraints. Every word earns its place, with no redundant or filler content.

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 absence of annotations and output schema, the description covers the core operational aspects: batch size, required fields, and atomic validation behavior. It does not explain the response structure or prerequisites (e.g., run must exist), but the provided schema and the key behavioral detail are sufficient for basic usage.

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 already provides 100% coverage with descriptions for all parameters. The description reinforces that each item requires test_id and status_id and clarifies that test_id is the per-run test id from testmo_list_results, which is already in the schema. Thus it adds minimal new semantic value beyond the structured data.

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 specific action: recording results for multiple tests in a run in a single request. It distinguishes itself from the sibling tool testmo_record_result by emphasizing 'multiple tests' and 'one request', making the bulk nature explicit.

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 implies the appropriate use case: when you need to record results for multiple tests at once rather than one by one. It also directs users to obtain test_id via testmo_list_results. However, it does not explicitly name alternative tools or state when not to use it, missing a stronger guideline.

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