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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral detail: the response is JSON with a fixed field set, and some groups may be flagged as temporarily down with an alternative group to use meanwhile. It does not mention result caps or ordering, which keeps it below 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?

The when-to-use condition is front-loaded and the return summary follows, which is the right order. The parameter sentence at the end largely repeats enum values already in the schema, so a small amount of text does not earn its place, and the opening sentence is a long run-on.

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 carries the burden of explaining return values and does so thoroughly, including edge-case behavior (temporarily unavailable groups). For a two-parameter read tool this is nearly complete; only result volume/ordering is unspecified.

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 the baseline is 3, but the description goes beyond it: it glosses the topic enum with 'premium (memberships by application)' and gives concrete query examples ('rolex, golf or sneakers'). That extra semantic detail about what 'premium' actually means and how the query string is used is real added value.

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 pairs a specific verb ('find') with a specific resource ('Moda's official groups for the topic') and even enumerates the return fields (name, purpose, access, member count, group link, Moda page, downtime notice, joining steps). An agent can immediately tell this is a community-discovery tool, distinct from lookup siblings like find_watch_by_name or search_moda_help.

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 opening clause gives a clear triggering condition: the user wants to buy, sell or talk about watches, cars, gold, jewelry or sneakers and asks which Moda community fits or how to join. It also inherits 'Use all when unsure' from the schema. It does not name a sibling to use instead when the question is really a help-content question, so it stops short of full routing guidance.

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