text-list

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

The description offers no information about side effects or lack thereof. Since it is a listing operation, it is presumably non-destructive, but this is not stated. No annotations compensate for this absence, leaving behavior opaque.

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 a single, concise sentence that directly conveys the action. It contains no filler or redundant words, making it highly efficient.

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?

The description lacks details about what the listing returns, such as the format or content of the list. Without an output schema, the agent is left without essential context about the expected result, which diminishes completeness.

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 tool has zero parameters, which establishes a baseline of 4. The description does not need to elaborate on parameter meanings, and no parameter information is expected or missing.

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 that the tool lists Text data-blocks, using a specific verb and resource. It distinguishes from sibling tools like text-create or text-read, but does not explicitly mention scope such as 'all' or filtering.

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 provides no guidance on when to use this tool versus alternatives. It does not indicate any specific scenarios or prerequisites, leaving the agent without direction on when listing is appropriate.

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