compost

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

The description does not disclose behavioral traits such as side effects, permissions, or state changes. With no annotations provided, the description carries full burden but omits critical details (e.g., whether surfaced threads are opened, marked, or listed).

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 consists of two short, relevant sentences with no wasted words. The first sentence states the action, the second provides usage guidance.

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 simple tool with one parameter and no annotations, the description covers purpose and usage adequately. However, it lacks behavioral transparency and does not describe the return value (output schema exists but is not detailed in the evaluation).

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 parameter 'n' is not described in the input schema (0% coverage). The description adds meaning by stating it controls the number of threads surfaced (default 2), but does not explain constraints or format. This is minimal compensation.

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 the tool surfaces N random idle threads, using a specific verb ('Surface') and resource ('idle threads'). It also provides metaphorical context for when to use it, distinguishing it from siblings like 'idle_thread' which may have a different focus.

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 suggests when to call the tool ('when current threads feel exhausted or you want to shake loose dormant ideas'), but does not explicitly mention alternatives or when not to use it. The guideline is implied rather than explicit.

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