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

annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuine value by disclosing that a single endpoint returns four distinct entity types, which an agent cannot infer from the type enum alone. It does not mention pagination behavior or the shape of the response, which matters for a 15-parameter list call.

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, zero filler, resource scope front-loaded before the API reference. Nothing here is redundant or padded.

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 15-parameter list tool with no output schema, the description says nothing about pagination defaults, result limits, or what a response contains. The schema carries the parameters well and the annotation covers safety, but an agent gets no sense of return volume or behavior at page boundaries.

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 all 15 filters, date ranges, sorting and paging parameters are documented in the schema itself. The description adds no extra semantics such as how date ranges are combined or whether filters AND together, so baseline 3 applies.

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 enumerates the four resource kinds returned (tasks, work orders, tenant requests, owner requests), which maps directly to the type enum. It clearly differs from doorloop_get_task (singular fetch) by naming, though the description never explicitly contrasts them.

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?

Usage is only implied by the verb 'List' and the endpoint GET /tasks. There is no statement of when to prefer this over doorloop_get_task for a single record, no prerequisites, and no exclusions. Adequate for a self-evident list operation but not informative.

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