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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description adds genuine context beyond that: results are ordered most-recent-first, each thread includes the last message and its author, and it requires a Cotlet API key with access to this app. Auth and ordering detail are real value-adds; return pagination is not described.

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?

Front-loads purpose and returns in two tight sentences, then tacks on the useful 'neighbors start these' semantics and auth requirement. All four sentences carry information; the auth sentence could arguably be trimmed but is not filler.

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?

There is no output schema, so the description bears the burden of explaining returns, and it does (last message, author, newest-first ordering). Read-only safety is covered by annotations. Missing pagination/next-page guidance and explicit sibling routing keep it short of full completeness.

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 100%, so both parameters (limit, unanswered_only) are already documented in the schema. The description adds only the 'most recent threads first' ordering note, which mildly relates to limit but adds no syntax beyond the schema. Baseline 3 is 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 (list) and resource (conversations) and scopes it precisely: messages neighbors sent to your Business Page, returning the last message and author, newest-first. This clearly distinguishes it from the singular nextdoor_get_conversation sibling without needing to open either 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?

The line 'Neighbors start these conversations; a business cannot start one' gives useful context about what these threads are and implicitly why you'd read rather than create one. However, it never explicitly states when to use this versus nextdoor_get_conversation (single thread) or nextdoor_send_message, leaving routing to inference.

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