echo_large

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

No annotations are provided, so the description carries the full behavioral burden. It discloses only that the output is deterministic and that size is approximate; it says nothing about side effects, content/encoding of the generated text, exactness of the size, or how it behaves differently from the sibling echo tool.

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?

A single short sentence with the verb and the key constraint front-loaded; nothing is redundant. It is tight, though the brevity is partly due to under-specification rather than efficiency.

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?

An output schema exists, so return values need not be described here. However, for a fixture-generation tool with an undocumented parameter and no annotations, the description leaves real gaps about generation format, size accuracy, and relationship to the other echo tools.

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 single size_kb parameter has 0% schema description coverage, so the description must compensate. It partially does by establishing the unit (kilobytes) and the 'approximately' caveat, but gives no valid range, bounds, or edge-case behavior (e.g., 0 or very large values).

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 concrete verb (Return) and resource (deterministic text of approximately N kilobytes), which is more specific than the bare name echo_large. It does not, however, distinguish this from the sibling 'echo' tool or explain what makes the output 'large' versus a normal echo.

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?

There is no guidance on when to use this tool versus the many echo-family siblings (echo, echo_nested, echo_types, echo_empty, echo_multiple, echo_schema, echo_error). No prerequisites, no exclusions, no indication of the intended use case (e.g., payload-size testing).

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