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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that this returns curated guide topics, but does not mention response format, pagination, or whether content is static versus dynamic.

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 front-loaded with the core purpose and then provides the topic list efficiently. It repeats the schema's 'omit topic to list all' instruction and uses 'and more,' which is slightly redundant, but overall every sentence contributes useful selection information.

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 single optional enum parameter with no output schema and annotations covering safety, the description provides enough context to choose a topic or list all. It does not describe all seven enum values by name, but 'and more' signals the remainder, which is adequate.

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 coverage is 100%, so baseline would be 3, but the description adds semantic meaning to several enum values: 'chambers' means which chambers work, 'install' means installing OpenShrooly firmware, and 'terrashroom' means keeping one running. This goes beyond the bare enum labels in the schema.

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 specific verb and resource ('Get Shroom Labs guides for automated mushroom grow chambers') and enumerates the topic families, so an agent knows this retrieves static guide content rather than profile or timeline data. It does not explicitly distinguish itself from siblings like search_grow_content, but the resource is clear.

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?

It says 'Omit topic to list all,' which gives one concrete usage behavior, but it does not state when to use this versus search_grow_content or the other sibling tools. Usage is implied by the topic list rather than explicitly guided.

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