foolish

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

With no annotations and no meaningful description, the tool's behavior is entirely opaque. The phrase 'returns foolish data' discloses nothing about side effects, permissions, rate limits, or return characteristics.

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 vague sentence, which is not conciseness but severe under-specification. It provides no structural value and leaves the reader with no useful information.

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 absence of annotations and output schema, the description carries the full burden of explaining the tool. It completely fails to do so, offering no context about what 'foolish data' is, how it is returned, or why an agent would invoke it.

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 and the empty schema already fully documents that. No additional parameter information is needed, so the description does not need to compensate. Baseline 4 for 0-parameter tools.

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 'Returns foolish data' merely restates the tool name 'foolish' with no verb or resource specification. It fails to convey what the tool actually does, what 'foolish' means, or how it differs from siblings like uselessfacts or yes.

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?

No guidance is provided on when to use this tool versus alternatives. The description gives no context for appropriate use, prerequisites, or exclusions.

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