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

Annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false) only cover the safety profile, while the description adds substantial context beyond them: the call fails for accounts pending business-document verification, there is a per-call confirmation default that can be disabled, and an API key requirement. This is rich behavioral disclosure.

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?

Purpose is front-loaded and most sentences carry distinct information (verification failure, confirmation default, API key). Slight redundancy between 'By default you confirm each call; you can switch that off' and 'Reaches other people: confirm with the user before each call' costs it a point.

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 non-destructive but outward-facing publish tool with no output schema, the description covers the failure modes, confirmation/privacy expectations, credential requirement, and the audience-setting caveat. Nothing an agent needs before calling is missing.

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 coverage is 100%, so the 3-baseline applies, and the description adds meaning on top: it clarifies that business posts have no fixed radius and that radius/neighborhoods only take effect where the post form still offers audience settings. That nuance genuinely constrains how the radius and neighborhoods params behave.

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 (publish) and resource (business post) plus the scope (neighborhoods you choose), which cleanly distinguishes it from siblings like nextdoor_list_posts and nextdoor_get_post. An agent can identify creation-vs-read without opening any 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?

Gives real usage context: it reaches other people and should be confirmed with the user each call, and it notes radius/neighborhoods only apply where the form still offers audience settings. It does not name a sibling alternative, so it stops short of an explicit when-not/when-instead routing.

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