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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds contextual information about what communities are and what the tool returns, but does not disclose any additional behavioral traits such as pagination behavior or rate limits. Since annotations carry the burden, this is adequate but not rich.

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 reasonably concise, with the core purpose stated upfront and supporting context (community definition, examples, usage tip) following. It avoids redundancy and each sentence adds information. It is slightly longer than strictly necessary but remains focused and well-structured.

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?

Given the output schema exists (so return format is defined) and annotations cover safety, the description covers the essential context: what communities are, what the tool returns, and how to use the result (community ID with the Zenodo website). It also provides examples and scale (5,000+ communities). No critical information is missing for 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?

The input schema provides complete documentation for all four parameters (100% coverage). The description adds value by giving concrete examples of valid query terms ('astronomy', 'bioinformatics', 'EU Horizon projects', 'CERN data'), which helps agents understand how to craft effective searches. This exceeds the baseline of 3.

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 clearly states the action (Search) and resource (Zenodo communities), and differentiates from the sibling zenodo.records.search by focusing on communities and explaining what they are. The examples of communities and the mention of returning IDs, titles, descriptions, and URLs make the tool's purpose unmistakable.

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 description provides clear context for when to use this tool: when searching for communities rather than records. It also gives practical guidance on how to use the returned community ID with the Zenodo website. However, it does not explicitly name alternative tools or state when not to use it, so it lacks explicit exclusions.

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