sii_persona_list_bienes_raices

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

With no annotations, the description carries the full burden. It discloses that this is a list operation, describes the scope (person RUT), and details the output contents including a summary. However, it does not mention potential pagination, error conditions, or explicitly state that it is read-only, though 'Lista' implies non-mutating behavior.

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 two sentences long, front-loaded with the core function, and every clause adds value—listing the data fields and then providing a critical note about the authentication scope. There is no redundant or filler content.

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 tool's simplicity (zero parameters, no output schema), the description is quite complete. It explains the data returned, the summary, and the key difference from company-level tools. Minor gaps include lack of return format specifics or error handling, but the provided details are sufficient for a straightforward list operation.

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 tool has zero parameters, so the baseline is 4. The description adds no parameter-specific information, but none is needed. It appropriately explains the operation's context and output without needing to clarify parameter usage.

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's function: 'Lista los bienes raíces (propiedades) del RUT persona autenticado en el SII' with a specific verb and resource. It also differentiates from siblings by emphasizing it operates on the person's RUT rather than an empresa, and lists the exact data fields returned.

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 provides clear context for when to use the tool: it is for the authenticated person's real estate properties, and explicitly states 'No requiere SII_EMPRESA_RUT: cuelga de la persona, no de la empresa,' which tells the agent not to supply an empresa context. While it doesn't name an alternative sibling tool, the scope distinction is clear.

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