list_tenants

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

With no annotations provided, the description discloses important behaviors: pagination limits (per_page up to 100, page 1-indexed) and time filter format (ISO 8601). It doesn't detail all return structure, but the output schema exists. No annotation contradiction.

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?

The description is extremely concise: three short sentences that front-load the purpose, then quick guidelines, then parameter constraints. Every sentence adds value without 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?

Given 7 parameters, the description covers pagination and time filters well but leaves out 'only_ids' entirely. The 'facility_id' is implied but not explicitly documented. Output schema exists, so return format isn't needed, but the missing parameter info creates a gap.

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 coverage is 0%, so the description must compensate. It adds meaning for pagination parameters and time filters, specifying constraints and format. However, it omits details for 'only_ids' and 'facility_id', though the latter is inferred from the purpose.

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?

The description clearly states 'List tenants for a facility' and provides concrete usage examples like 'show me all tenants' and 'list tenants moved in this month'. It effectively distinguishes from siblings such as search_tenants (search) and list_current_tenants (current only).

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 'Use when' section gives clear context and example queries, but does not explicitly state when not to use this tool or mention alternatives like search_tenants for more advanced filtering. Still, the guidance is sufficient for common use cases.

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