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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the closing "Safety: Closed-world..." sentence largely restates them. The genuinely additive behavioral content is the requirement that MCP clients convert UTC starts_at/ends_at into the lodging timezone before display, which is real context not captured by annotations, though return shape and completeness are left unaddressed.

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?

Four short sentences with no repetition, though the first is a bare fragment and "Supports common list filters" is low-value filler that could be replaced with concrete filter behavior. Front-loading is acceptable but the purpose clause is the weakest part.

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 an output schema present, return values needn't be explained, and the timezone-display note covers client-side handling well. However, for a seven-parameter list tool the description says nothing about pagination/result limits, ordering, or the incremental-update behavior implied by updated_since and deleted filters.

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 description coverage is 100%, so the schema already documents all seven parameters, and the baseline is 3. The description adds nothing about the actual list parameters and never clarifies the schema's notable oddity that activity_type and transportation_type are marked 'only used by activities/transportations' — i.e., effectively inert for hostings.

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 opens with the noun fragment "Hotel and lodging plans," which names the resource but never states the action (list/retrieve) or the scope (per-trip). The verb is only recoverable from the tool name and the sibling set (tripsy_hostings_create/show/update/delete) rather than from the text itself.

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?

"Supports common list filters" is the only usage statement and it is vague rather than directive. There is no guidance on when to use this versus tripsy_hostings_show for a single hosting, no note on whether results are paginated or complete, and no exclusions.

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