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

readOnlyHint=true already tells the agent this is a safe read, so the description's job is lighter. It adds useful context that tasks carry assignee/status/cost and that it maps to hostaway GET /v1/tasks, but says nothing about pagination behavior or default ordering beyond what limit/offset in the schema imply.

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?

Front-loaded with purpose, then filters, then endpoint - three compact sentences with no redundancy. The trailing 'Hostaway: GET /v1/tasks' adds little operational value but is brief enough not to hurt.

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, all-optional read tool with no output schema, the description covers what is returned and what can be filtered, which is enough to invoke it correctly. Minor gaps remain around result volume/paging expectations, but the schema carries limit/offset.

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 baseline is 3. The description groups the four oddly named date parameters into 'start/deadline windows', which lightly clarifies intent, but it adds no syntax or format detail beyond what the parameter descriptions already provide.

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: cleaning, maintenance, check-in/out), and even enumerates the fields returned (assignee, status, time window, cost). This clearly separates it from sibling hostaway_create_task and hostaway_update_task without needing their schemas.

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 description tells the agent which filters are available (reservation, status, text match, channel, start/deadline windows), which implies usage, but never states when to reach for this tool versus alternatives such as hostaway_get_reservation or hostaway_list_reservations. Usable but leaves selection to inference.

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