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

No annotations are supplied, so the description carries the full disclosure burden, and it says nothing about what a call with no arguments returns, whether both parameters can be combined, or what any precedence rule is. It conveys content scope but not behavior, and gives no sense of result shape or size.

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 front-loaded sentence with no filler, and the topic enumeration is compact via inline glosses. The nested parentheses around the second and third topics make it slightly harder to parse than a clean list would be.

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?

There is no output schema and no annotations for a two-optional-parameter tool with zero required arguments, so the definition should at minimum resolve the zero-argument case and the topic-vs-q relationship. It resolves neither, though the topic glosses make the tool usable in practice.

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%, so the description must compensate: it does a good job explaining what each of the three enum values contains (field-guide, life, identify). The `q` parameter, however, gets only 'Or search with q' — no indication of what is searched or whether a topic and q interact, leaving half the parameters under-explained.

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?

States the resource (trout knowledge from the site) and enumerates the three content areas covered, so an agent can see this is static reference content rather than Q&A or jokes. It never names the sibling it complements most closely (answer_trout_question), so the differentiation is implicit rather than explicit.

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?

'Or search with q' implies two calling modes (browse by topic vs. free-text search), which is the only usage guidance present. There is no statement of when to pick this over answer_trout_question or trout_lab, nor what happens if neither parameter is supplied.

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