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

With no annotations supplied, the description bears the full burden of disclosing behavior. It reveals nothing about side effects, data sources, rate limits, or output structure. The phrase 'Find something to do' implies a read-only operation but does not explicitly confirm safety or any limitations.

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 short (one phrase), which is concise but not effective. It under-specifies behavior and context, resembling a placeholder more than a helpful definition. The lack of detail outweighs the benefit of brevity.

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 trivial tool with no parameters and an output schema (not shown but indicated), the description should at least hint at the returned data or confirm it provides a random/recommended activity. It does neither. Moreover, the close sibling 'suggest_activity' creates ambiguity that the description fails to resolve, leaving the definition incomplete.

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 schema coverage is 100% (there is no schema to cover). Per the rubric, a zero-parameter tool gets a baseline of 4 because there is no parameter semantics to clarify. The description adds no value here, but none is required.

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 'Find something to do when bored' clearly states a verb ('find') and a resource ('activity to do when bored'), making the core purpose obvious. However, it makes no attempt to distinguish itself from the sibling tool 'suggest_activity', which appears to serve a nearly identical purpose.

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 choose this tool over 'suggest_activity' or other entertainment tools like 'fetch_joke' or 'get_advice'. The description gives no context, prerequisites, or exclusions, leaving the agent to guess which tool is appropriate.

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