list_leases

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

The description discloses that it returns a dictionary with leases list and metadata, and mentions optional filters and pagination. However, it does not disclose access control, sorting behavior, or any side effects, and there are no annotations to supplement this. It is minimally transparent.

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 structured with Args and Returns sections, each line adding value by documenting a parameter or return format. It is efficient but slightly verbose due to listing all parameters; still appropriate given the schema's lack of descriptions.

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 an output schema present, the description need not detail return fields, but it still confirms the return type. Given that all parameters are optional and straightforward, the description sufficiently covers the tool's context for an agent to invoke it correctly.

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 Args section explicitly describes each of the five parameters, including their purpose and defaults (e.g., limit default 100, offset default 0). This fully compensates for the 0% schema description coverage, providing clear semantics.

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 name 'list_leases' and description 'List leases from Buildium' clearly define the operation and resource. It differentiates from get_lease (single) and create/update leases, and from list_lease_transactions.

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?

No guidance is provided on when to use this tool versus alternatives like get_lease or list_lease_transactions. The description does not mention scenarios for filtering or when to use pagination parameters, leaving the agent to infer usage.

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