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

Annotations already cover safety (readOnlyHint, openWorldHint=false), but the description adds non-obvious behavior beyond them: the default exclusion of Off-menu content and the guarantee that Off-menu results always carry a legal notice. That legal-notice behavior is something an agent could not infer from annotations or schema, which is exactly the extra context worth crediting.

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?

Three tight sentences: what it is, what each record contains, and the off-menu opt-in caveat. The most decision-relevant framing (identity and content shape) is front-loaded, and no sentence is filler.

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?

With no output schema, the description usefully discloses the return shape (slug, total grow days, canonical URL) and the legal-notice behavior for Off-menu items, which covers the main gaps. Minor omissions remain — no hint about result ordering, count, or pagination for a list endpoint — but nothing blocks 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?

Schema coverage is 100%, so baseline is 3: both 'query' and 'include_off_menu' are documented with examples and defaults in the schema itself. The description reinforces the include_off_menu default and its consequence, but adds no syntax, format, or matching semantics beyond what the schema already provides.

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 a specific verb+resource ('List Shroom Labs mushroom grow profiles') and immediately scopes it with examples (lion's mane, pearl oyster, shiitake). It also names the sibling relationship ('a slug for get_profile'), so an agent can distinguish it from get_profile and search_grow_content without opening any schema.

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?

Gives clear default behavior ('culinary only by default') and the exact condition to widen scope ('set include_off_menu to also list educational Off-menu profiles'), plus a forward pointer to get_profile via slug. It stops short of explicitly ruling out search_grow_content as the alternative for free-text discovery, so it's strong but not a full when/when-not guide.

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