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

The description matches the annotations: destructiveHint=true and readOnlyHint=false, and idempotentHint=true is consistent with a replace operation. Beyond the annotations, it discloses that the tool is the only writable field on a Load Test, that it overwrites the entire notes, and that an empty string clears notes. Minor gap: it doesn't mention potential effects on other users or restore/versioning, but it adds substantial context.

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-loads the core behavior, and every sentence earns its place. It covers the action, the guardrail, and the overwrite caveat without fluff.

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 no output schema and three required parameters, the description addresses the critical operational context: when to write, what to preserve, and the full-replacement behavior. The sibling list and annotations cover the rest, so an agent has enough to invoke it correctly.

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 coverage is 67% and the description adds meaningful semantics beyond the schema: it emphasizes that notes replaces the entire report notes, advises reading current notes first to preserve content, and clarifies the user-ownership aspect. This goes beyond the schema's basic parameter descriptions.

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 specific verb and resource: it replaces the notes on a Load Test's Test Report, emphasizing that it is the only writable thing on a Load Test. This distinguishes it from all sibling update tools and get_load_test_report.

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?

It gives explicit when-to-use guidance: ask the user before writing, never write when merely advising on a test. It also directs the agent to first read the current notes with get_load_test_report and preserve the user's content, and warns that the text sent becomes the entire notes.

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