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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds a genuinely non-obvious epistemic caveat — the result is an authored, bounded prediction and explicitly 'not empirical evidence' — which is exactly the kind of trust/usage context annotations cannot convey. It stops short of describing output form or parameter effects, hence not a 5.

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?

A single clause with the key limitation front-loaded and no filler. It is efficient, though its brevity borders on under-specification for a tool with three unlabeled numeric parameters.

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 three parameters at 0% schema coverage and no output schema, the description does not explain what the inputs control or what comes back. The one behavioral caveat is useful, but the definition is not complete enough for an agent to call it confidently.

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?

Schema description coverage is 0% and the description says nothing about hours, power, or resolution — only the word 'bounded' faintly alludes to the min/max clamps in the schema. With three undocumented parameters, the description fails to compensate for the coverage gap.

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 names a verb and resource ('Run a bounded authored thermal prediction'), which is more than a tautology. However, the terminology is opaque — 'authored', 'bounded', and the relationship to the tool name 'hidden world' are unexplained, and no sibling tool shares this domain, so there is nothing to differentiate against. It signals a simulation-ish operation without making the actual purpose concrete.

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 on when to invoke this tool versus alternatives, no prerequisites, and no indication of what inputs make sense together. The only orienting statement is the negative 'not empirical evidence', which hints at how to treat output but not when to call it.

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