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

No annotations are provided, so the description carries the full burden, and it does convey that the output is informational reference content rather than an action, and that some of it is time-sensitive ('today's streaming hours'). It never explicitly states it is read-only with no side effects, and doesn't indicate output format or length, which keeps it from 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 sentence, front-loaded with the routing imperative 'Start here' followed by a compact content list. No filler, nothing redundant with the title, and every clause adds a distinct piece of scope.

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 tool with no output schema, the description substitutes well by enumerating the returned content categories, which is the one thing an agent needs in order to decide to call it. Nothing else is required for correct invocation.

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 takes zero parameters and the description correctly presents no parameter discussion, avoiding invented inputs. Baseline 4 applies since there is nothing to mis-specify and the empty schema leaves no ambiguity.

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 enumerates exactly what the tool covers — trout cam overview, detection method, today's streaming hours, watch links, data sources, citation — which is precisely the content space of an 'about' tool. This distinguishes it clearly from Q&A, joke, fact, and now-playing siblings without needing to name them.

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?

'Start here' gives an explicit entry-point directive, telling the agent this is the onboarding/orientation call. It stops short of naming alternatives (e.g., use trout_now for live status, answer_trout_question for specific queries) or stating when not to use it.

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