Buildium Get Lease

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, fully covering safety and idempotency. The description adds minimal behavioral context beyond 'including tenants and rent terms', which relates to response content rather than side effects. With annotations present, the bar is lower, and this modest addition earns a 3.

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, focused sentence that conveys the core purpose without redundancy. It is front-loaded with the action and resource, making it easy to scan. No wasted words.

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 that an output schema exists (so return structure is defined), the annotations cover safety, and the schema documents parameters fully, the description is sufficient for an agent to invoke the tool correctly. It states exactly what the tool does, and the schema fills in the rest. Nothing critical is missing.

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%, so both parameters (lease_id and fields) are already described in the schema. The fields parameter's schema description is notably detailed, explaining its purpose and why it's useful. The tool description itself does not add any parameter-specific information, but since the schema carries the burden, the baseline of 3 is appropriate.

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 the action ('Get'), the specific resource ('one lease'), and the key included details ('tenants and rent terms'). It is distinguishable from siblings like buildium_list_leases, which implies retrieving multiple leases, and from buildium_get_rental, which targets a different resource.

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 description implies usage: use this when you need a single lease by ID. It does not explicitly name alternatives or exclusions, but the phrase 'one lease by ID' sets clear context. A slight gap is the lack of guidance on when to prefer list_leases or other tools, but the purpose is clear enough for most agents.

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