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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description's added value is in explaining the `yourAi` mode semantics: off means don't act, draft means the user taps cards, manage means acting as the place in its AI log with Undo. That is genuinely useful behavioral context an agent could not get from the annotations, and the ownership rule reinforces that these settings are human-controlled.

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?

It is short, which is good, but the first sentence is a run-on that nests an enumerated mode explanation, and "Also asks and the inbox's unread" is a telegraphic fragment with no verb. The mode semantics are worth keeping; the phrasing around them costs readability.

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 output schema, the description must say what comes back, and it does: places, each place's AI mode, asks, and unread inbox counts. For a zero-parameter read-only tool that is close to complete, though it says nothing about ordering, pagination, or how the three modes affect what the agent can subsequently do.

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, which is the baseline-4 case; there is nothing for the description to disambiguate. The inline gloss on the three `yourAi` values describes returned data rather than inputs, but it is still the most informative part of the definition.

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 conveys that this returns the places the user runs along with their per-place `yourAi` setting, asks, and unread inbox counts, so the resource is identifiable. But it opens with the fragment "The places they run" with no explicit verb, and the title ("Places you run and your AI's say there") is equally fractured, so an agent must work to confirm this is a read-only listing tool.

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?

There is one hard constraint — "Only the person sets it, never you" — which usefully tells the agent not to write, but no when-to-use guidance at all. It never distinguishes this from close siblings like place_settings, place_stats, list_members, or read_place_inbox, even though it overlaps with the last of those in returning unread counts.

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