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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds genuinely new context: it is free (no quota cost), the data is opt-in and anonymized, and private project labels are excluded. Return format and pagination are left unaddressed.

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 short front-loaded clauses with no filler; the cost and privacy qualifiers arrive before the filtering detail. Slightly clipped to the point of under-specification rather than being verbose.

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?

An output schema exists, so return values need no explanation, and the read-only annotations cover the safety profile. For a simple two-parameter read tool the description supplies the essential context (free, anonymized, domain-filtered, no private labels); only the 'limit' parameter is a residual gap.

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 carry the load. It explains that 'domain' is a filter, but 'limit' is never mentioned and no format, enum, or default is given for domain either, leaving half the parameter surface undocumented.

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 and resource ('browse opt-in community feature patterns') plus a scope exclusion ('does not include private project labels'), which distinguishes it from private-memory siblings like list_feature_memory. It never names those siblings, so differentiation requires inference.

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 'does not include private project labels' clause implicitly tells the agent when this tool is wrong (private data), but no alternative such as list_feature_memory or publish_feature_pattern is named, and there is no guidance on when the community corpus is the right source.

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