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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds value beyond that: a specific failure mode (no claimed Business Page) and an auth requirement (Cotlet API key with access to this app), both of which shape whether the agent should even attempt the call.

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-loaded with the purpose and return contents, then the usage hint, then failure and auth conditions. The colon-separated field list is slightly listy but every element (including the create_post tie-in) 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?

With no input parameters and no output schema, the description carries the burden well: it describes what comes back, the failure condition, and the required credential. Missing only a note on whether the page is always singular/one-per-account edge cases, which is minor.

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?

The tool takes zero parameters, so there is no parameter semantics burden to compensate for. The description's field enumeration is about the return payload rather than inputs, which is appropriate here.

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?

It names a specific verb (get) and resource (the signed-in account's Business Page) and enumerates the returned fields (name, category, contact details, neighborhoods, recommendation and Fave counts). This distinguishes it clearly from siblings like nextdoor_get_page_share_link and nextdoor_list_posts 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?

It gives concrete downstream context ('Use the neighborhoods it lists as the audience for create_post') and a precondition (fails without a claimed Business Page). It stops short of naming an alternative getter tool or stating when-not to use it, but the context is clear.

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