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

The annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds that prospects are included alongside lease tenants and that contact details are returned, plus the underlying endpoint, but says nothing about pagination totals, maximum result sets, or ordering defaults beyond what the schema documents.

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, front-loaded sentences with the resource and scope stated immediately. The trailing 'DoorLoop API: GET /tenants' is mild filler for an agent but is harmless and grounds the tool in the vendor API.

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 no output schema, the description should at least sketch the return shape; 'contact details' is a partial hint but doesn't cover the tenant record structure or pagination metadata. For a read-only list tool with fully documented parameters this is adequate but incomplete.

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 filter, page_size bounds, and sort flags are already documented in the schema. The description adds no additional semantics about filtering or how filters combine (AND vs OR), which is the one gap the schema leaves.

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 and resource ('List tenants and prospects'), and adds what the results contain ('contact details'), which goes beyond the title. It does not distinguish itself from the close sibling doorloop_list_lease_tenants, so an agent could still hesitate between the two.

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 through the available filters; there is no statement of when to use this versus doorloop_get_tenant (single lookup) or doorloop_list_lease_tenants (tenants on a lease). For a tool with 10 optional filters and several near-neighbor siblings, that omission leaves real ambiguity.

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