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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context beyond annotations: results are returned newest first, the exact return fields are listed, and the tool requires a Cotlet API key with access to the app. It does not describe pagination behavior beyond the limit field.

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 front-loaded and mostly efficient, covering purpose, return order, return contents, and auth in four sentences. It is slightly repetitive in mentioning 'your reply' and then 'your existing reply if you wrote one'.

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 read-only list tool with complete schema coverage, safety annotations, and no output schema, the description supplies what is needed: the source section, returned fields, ordering, and auth requirement. Nothing further is required to call it correctly.

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 all three parameters (limit, since, unanswered_only) are already documented in the schema. The description does not add syntax, format, or meaning beyond what the schema provides, aside from obliquely referring to existing replies, which maps weakly to unanswered_only.

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 states a specific resource — recommendations from the 'What neighbors say' section — and lists the returned fields (author, neighborhood, text, date, reply). It distinguishes itself from reply_to_recommendation by noting it supplies the needed ID, but does not explicitly differentiate from sibling list tools like list_comments or list_posts.

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?

Usage is implied rather than stated: the description says each recommendation has the ID that reply_to_recommendation needs, suggesting it is the tool to call before replying. There is no explicit when-to-use/when-not guidance or named alternative for listing other Nextdoor content such as comments or posts.

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