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

The annotations already declare this as read-only, idempotent, non-destructive, and closed-world. The description adds useful content-level behavior: it includes ordered blocks and audience while excluding credential secrets, which tells the agent what data is safe to expect and what is omitted.

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 two compact sentences with no wasted words. The purpose and inclusion/exclusion notes are front-loaded and easy to parse.

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 read-only annotations and the presence of an output schema, the description covers the important selection and content context well: when to use it and what the returned definition includes or excludes. The main remaining gap is the 0% input-schema description coverage for testId, which the description does not compensate for.

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 0% for the sole required parameter, testId. The description never mentions testId, its expected format, or how to obtain it, so it adds no meaning beyond the raw schema pattern.

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 gives a specific read action and enumerates the test definition's contents: current draft, revision, validation, editability, ordered blocks, and audience. It is clear what the tool retrieves, though it does not explicitly contrast itself with siblings like get_test or list_test_blocks.

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?

"Read ... before editing" gives a clear usage context: this tool is for preparing an edit. It does not name alternatives or state when not to use it, but the intended moment of use is explicit.

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