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

readOnlyHint=true already declares this is a safe read, so the bar is lower. The description adds useful context by mapping to the underlying GET /v1/tasks endpoint and naming the return fields (assignee, status, time window, cost), but says nothing about pagination behavior or ordering despite limit/offset parameters.

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 compact sentences: the first front-loads what is listed and what comes back, the second covers filtering and the API mapping. No filler or redundancy.

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 10-parameter list tool with no output schema, the description supplies the return-field summary and all filter categories, which is nearly enough. The only real gap is pagination/ordering behavior, which isn't covered by annotations or an output schema.

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 every parameter is already documented in the schema (including the status enum and date patterns). The description restates the filter dimensions but adds no syntax, format, or precedence detail beyond what the schema provides – baseline 3.

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?

States a specific verb (List) and resource (operational tasks) and even enumerates task types (cleaning, maintenance, check-in/out). It is clear what the tool does, but it never names its create/update_task siblings or explicitly frames itself as the read counterpart, so sibling differentiation is left to the name.

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?

The second sentence enumerates filter dimensions (reservation, status, text match, channel, start/deadline windows), which is capability description rather than when-to-use guidance. There is no statement of when this tool should be chosen over hostaway_list_reservations, hostaway_create_task, or hostaway_update_task, and no exclusions.

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