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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds real behavioral context beyond annotations — the shape of results (themed sections vs cross-city carousel) and the hard constraint that only eight regions resolve. It doesn't note auth or rate limits, but those are minor for a public browse.

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?

Two dense sentences, with the core purpose front-loaded and the constraint placed last. The parenthetical example lists are useful but make the second sentence long; overall efficient with little waste.

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 single-optional-parameter browse tool with rich annotations and no output schema, the description covers purpose, parameter effect, and the key misuse guard (unsupported cities). Nothing needed to call it correctly 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 enum and per-value meaning are already documented, which sets a 3 baseline. The description exceeds that by describing the effect of supplying vs omitting the parameter (themed sections vs trending carousel) and explicitly warning there is no broader city parameter.

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 verb (browse) and resource (Partiful's public explore page) and enumerates the content type (parties, pop-ups, panels, meetups). It is clear what the tool returns, but it never names or contrasts with the sibling partiful_event, so sibling differentiation is absent.

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 explicit conditional guidance: pass a region for a richer themed set, omit it for the top-level cross-city trending carousel. That tells the agent when to use the parameter but offers no alternative-tool routing and no exclusions against siblings.

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