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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, covering the mutation and safety profile. The description adds an ownership requirement and implies a partial update of listed fields, which is useful context. It does not contradict annotations, but it does not describe patch semantics or error cases.

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 entire description is two short sentences with the key action and requirement front-loaded. No filler words or redundant restatements of the title; it earns its place.

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?

The description gives the essential action, target resource, ownership prerequisite, and a representative field list, while the schema supplies all parameter constraints and annotations handle idempotency/destructiveness. Its completeness is undercut by the omission of two editable parameters (short_description, home_city) from the enumeration, which could mislead an agent into thinking they are not updatable. Overall adequate but with clear gaps.

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 compensate. It lists common editable fields (name, description, category, privacy, tags, icon, cover) and mentions required community_id, but omits short_description and home_city, and doesn't add details about enum values or null semantics. It adds the ownership constraint beyond the schema but only partially maps the parameter space.

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 opens with 'Edit a community you own,' a specific verb and resource, and enumerates the editable fields. This clearly differentiates it from create_community (create vs edit) and other resource-specific update tools, so an agent can select it correctly.

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?

It states the prerequisite 'Requires community_id; you must be its creator,' which tells the agent when this tool is valid (only for communities the user owns). It does not explicitly name alternatives or state when not to use it, but the ownership condition provides clear usage context.

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