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

With no annotations, the description must carry the behavioral burden. It discloses the returned content and output style ('told by Old Gravel in Troutish with English translations'), and 'Live state' implies a read-only observation, but it does not explicitly confirm side effects, freshness guarantees, or response format.

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 efficient sentence that front-loads the live cam state and then lists the returned observations. The persona and language detail adds flavor but remains relevant to the output style.

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 zero-parameter, read-only tool with no output schema, the description sufficiently explains what the agent will get: fish in view, water clarity, recent events, and translation context. It is nearly complete, though 'recent events' remains somewhat vague.

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, so parameter semantics are not a concern. The baseline for a zero-parameter tool is 4, and the description does not introduce confusing parameter-like expectations.

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 identifies the resource and scope: a live underwater trout cam in the Wasatch Range, returning fish in view, water clarity, and recent events. It is specific enough to distinguish this from a diary or Q&A sibling, though it does not explicitly name alternatives.

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 phrase 'Live state' implies this tool should be used for current conditions rather than historical or conversational trout tools. However, it never explicitly states when to use it versus siblings like trout_diary or answer_trout_question.

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