List Properties

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds the specific fields returned, which is useful but does not disclose additional behavioral traits such as pagination behavior or filter effects.

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 concise in English, but includes a full Spanish translation which, while helpful in bilingual contexts, adds redundancy. It is front-loaded with the primary purpose. Could be slightly more streamlined.

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 the presence of an output schema and 100% parameter coverage, the description is mostly complete. However, it says 'list all rental properties' which may mislead regarding pagination (since after and offset imply partial results). The description does not mention pagination or filtering capabilities, so it lacks full context.

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% and every parameter (q, after, limit, fields, offset, isActive) is described in the schema. The tool description does not add any extra meaning or context beyond what the schema provides, so it meets the baseline.

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 tool lists all rental properties for the workspace and explicitly lists the returned fields (name, address, capacity, owner info, license number). The verb 'List' is specific and distinguishes this from sibling tools like 'list_clients' or 'list_reservations'.

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 when a list of properties is needed, but it does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention when not to use it. No exclusions or context for alternative tools are given.

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