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

With no annotations, the description carries the burden. It discloses that the passage is random ('drawn at random') and that no input is needed ('asks nothing of you'), but it does not explicitly state whether there are side effects, network calls, or other behaviors. The lack of annotations makes this only partially transparent.

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 extremely concise, consisting of two short sentences. The core information (random passage) is front-loaded in the first sentence, and there is no unnecessary verbosity.

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?

For a tool with no parameters and no output schema, the description is largely sufficient. However, the phrase 'Same rules as the payload' is cryptic and may confuse an agent without additional context. Overall, the purpose is conveyed well enough for a simple random-passage tool.

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 input schema is an empty object with 100% coverage, so the baseline is 3. However, the description reinforces that there are no parameters by saying 'asks nothing of you', which adds a small semantic clarification beyond the schema.

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 states 'One short passage, drawn at random' which clearly indicates the tool returns a randomly selected passage. Although it does not use an explicit verb like 'returns', the intent is understandable. The phrase 'Same rules as the payload' is somewhat ambiguous and could be clearer.

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 explicit guidance on when to use this tool versus alternatives. It only hints at the non-urgent, no-input nature ('asks nothing of you and nothing in it is urgent'), but does not explain scenarios or contrast with sibling tools.

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