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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds only the raw REST path, which is redundant with the tool name and conveys no behavior beyond structured fields — no pagination, ordering, or return-shape context.

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 short sentences, front-loaded with the purpose. The trailing HTTP endpoint restates what the name already says and is the one sentence that doesn't fully earn its place.

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?

A simple single-parameter read tool whose annotations cover the safety profile, so little prose is needed. However, an agent still doesn't know whether results are paginated or how tasks are ordered, which matters for a list endpoint.

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 single property_id parameter has 0% schema description coverage, so the description must carry the burden. 'associated with a property' implies the param identifies the parent property, and the path template reinforces this, but nothing states that it must be a positive integer or where to obtain it.

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 (tasks) scoped to a property, which is clear enough to distinguish from the singular opentoclose_get_property_task. It doesn't explicitly name that sibling or any other alternative, so differentiation relies on the agent noticing the plural/list naming.

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 guidance on when to use this versus opentoclose_get_property_task or the other list_* property tools, and no mention of expected result volume or filtering. The agent must infer that this returns all tasks for a property with no filter options.

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