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

Annotations declare readOnlyHint=false, openWorldHint=true, destructiveHint=false; the description adds meaningful context beyond them—authorization requirements, the confirmation-by-default behavior, and that a deleted post cannot be restored with one call. The 'cannot be restored with one call' phrasing is slightly ambiguous versus the non-destructive hint, but it does not clearly contradict it.

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?

Content is front-loaded with the action and scope, then permissions, then safety guidance. It is slightly repetitive on confirmation ('By default you confirm each call' followed by 'confirm with the user before each call'), but overall tight and purposeful.

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 adequately covers the key facts an agent needs for a delete operation: authorization, confirmation policy, recoverability, and API key requirements. Only the exact return/result shape is unaddressed, which is a minor 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?

There is a single parameter with 100% schema description coverage ('Post ID from list_posts.'), so the schema already carries the parameter semantics. The description adds nothing about post_id, making the baseline 3 appropriate.

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 ('Remove one of your business posts') with clear scope ('from the newsfeed'), distinguishing it from siblings like nextdoor_create_post, get_post, and list_posts. An agent can identify the operation without opening the schema.

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?

Provides explicit conditions: only the author or page administrator may delete, and it instructs the agent to confirm with the user before each call because it reaches other people. It stops short of naming alternatives, but the context and preconditions are clear.

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