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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the bar is lower. The description adds genuine non-annotation context with 'Claims remain self-declared,' warning that profile data is unverified and owner-asserted — useful trust information. It stops there, saying nothing about result ordering, pagination via cursor, or what 'explicitly published' excludes.

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?

Two short sentences, zero filler, with the core scope statement front-loaded and the trust caveat second. It is efficient, though arguably too terse given a six-parameter search surface, which keeps it short of a 5.

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 tool with six filter parameters, no output schema, and no per-parameter documentation, two sentences are not enough. The agent cannot tell what a profile record contains, how results are ordered or paged, or how the filters combine, so the definition is materially incomplete for its complexity.

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% across six parameters, and the description supplies no parameter meaning at all — nothing about 'q' as a search string, the role/topic enum values as filters, 'limit' as page size, 'cursor' for pagination, or what 'include_synthetic' toggles. With six undocumented filters, the description does not compensate for the coverage gap.

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 ('Find profiles') plus a scope qualifier ('explicitly published by owners'), so an agent knows this is a discovery/search operation rather than a single lookup. It does not, however, distinguish itself from the sibling 'community_profile' (singular), leaving the agent to infer the plural-vs-singular split from the name alone.

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?

There is no guidance on when to use this tool versus community_profile, community_feed, community_post, or community_contract. No prerequisites, no excluded cases, no mention of pagination or how to narrow results — the agent gets a purpose but no routing logic.

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