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

No annotations are provided, so the description carries the full behavioral disclosure burden, but it says nothing about whether this is a read operation, an external API call, what it returns, or any side effects. The text reveals zero behavioral traits.

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?

Although the description is extremely short, this is under-specification rather than useful conciseness. The phrase 'Bored API: Bored API' wastes words because it simply repeats the name without earning its place.

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 one parameter, no annotations, and no output schema, this description is completely inadequate. An agent cannot determine what outcomes to expect, what values of 'type' are valid, or what 'bored' even means in this context.

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 has 100% description coverage for the single 'type' parameter, so the schema carries the documentation burden. The tool description itself adds no meaning beyond the schema, but the high schema coverage keeps this at the baseline of 3.

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 is literally "Bored API: Bored API", which merely restates the tool name and provides no verb, resource, or behavior. With thousands of sibling tools, the agent has no way to know what this tool does.

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 about when to use this tool, what inputs are appropriate, or which alternatives may be relevant. The description contains no contextual or comparative information at all.

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