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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds real value beyond that by disclosing the return payload: required secret keys per app, plan entitlement, current connection state with last sync, and calendar feedId. No output schema exists, so this return-shape disclosure is the only source of that information.

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 a single sentence with no padding, but it is front-loaded with brand-name enumeration (Hospitable, Hostaway, Guesty, Airbnb, Vrbo...) rather than the core action. The most decision-relevant information — plan availability, connection status, feedId — is buried at the end.

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 one-parameter read-only list tool, the description covers the important unknown (what the rows contain) in useful detail, which compensates for the absent output schema. The remaining gap is that the 'id' parameter's site scoping and the list/array return nature are left implicit.

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% with a single required 'id' (documented as 'Site id.'), so the schema carries the burden. The description adds nothing about what the id scopes — it never says the listing is per-site, which is the one piece of meaning the schema does not convey.

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 enumerates what kinds of apps exist (rental tools, calendar links, feeds/shops, Airtable) and what the response reveals, so an agent can infer this is a catalog of available integrations. But it never states a verb or object directly — 'Apps that fill a collection' is a fragment, not a statement that the tool lists available apps for a site. It is distinguishable from connect_app/set_integrations by its inventory framing, but only by inference.

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 no explicit when-to-use guidance and no named alternative. The mention of 'what each needs (secret keys marked), whether the plan has it' hints at a pre-connection discovery step, but the agent must guess that this is the tool to call before connect_app or set_integrations.

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