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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior: the tool opens nothing by itself, and the absence of an official Business Page API is why browser automation is required. It does not say what happens if the user is not signed in or has no Business Page, so the added context is real but partial.

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 operational content is front-loaded well, but 'from ChatGPT, Claude or any AI agent' is marketing filler, and the final sentence repeats 'Nextdoor' twice to deliver one fact (no official API, with a check date). Removing the filler would leave a tighter, equally informative paragraph.

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 zero-parameter, no-output-schema guidance tool, the description supplies what an agent needs: what it returns, that it performs no action itself, and which tools carry out the task. The remaining gap, preconditions such as login state or Business Page ownership, 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?

There are zero input parameters, so the baseline of 4 applies; the schema is fully self-describing and the description has no parameters to explain. Nothing in the text adds or obscures parameter meaning.

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 names a specific verb and resource (page stats in the user's own Nextdoor account) and makes clear that the tool returns step-by-step instructions rather than data, which corrects the impression created by the name 'get_page_stats'. An agent that reads the whole text can tell it apart from the data-returning siblings, though the opening sentence 'Get page stats' still invites a misread that must be resolved by the second sentence.

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 an explicit two-step workflow: call this to get the screens/buttons/fields, then execute with the cotlet_browser_* tools in the user's Nextdoor Cloud Browser. It does not name exclusion cases (for example, when a sibling guide tool such as cotlet_app_guide would be preferred), but the context for use is unambiguous.

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