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

The readOnlyHint annotation already establishes the safe read profile, so the bar is lower; the description adds real value by disclosing the returned payload composition (tenants, cosigners, account details, move-out data). It also cites the underlying API endpoint, though it does not discuss auth requirements or whether missing ids error versus return empty.

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?

A single front-loaded sentence that names the operation and its payload, followed by a compact API reference. No filler, nothing repeated.

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 one-parameter read with readOnlyHint and no output schema, the definition is nearly complete: it tells the agent what data comes back. It omits only edge-case behavior such as not-found handling, which keeps it short of a 5.

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 100% for the single lease_id parameter, so the schema already carries the semantics and a 3 baseline applies. The description only restates that the fetch is keyed by id, adding no format or constraint detail beyond the schema.

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 ('Fetch') and resource ('one lease by id') and enumerates the included data (tenants, cosigners, account details, move-out data). The singular 'one lease' cleanly distinguishes it from the sibling buildium_list_leases.

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 implied by 'by id' versus the list counterpart, but the description never states when to prefer this tool over buildium_list_leases or buildium_list_lease_transactions. No exclusions or preconditions are given.

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