gerent365_get_business

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

No annotations are provided, so the description must carry the behavioral transparency burden. The verb 'obtiene' implies a read-only operation, but the description does not explicitly state safety side effects, authentication requirements, or potential errors. It is a simple getter, so the implied behavior is clear, but there is no additional detail beyond the action itself.

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 a single, front-loaded sentence in Spanish. It is concise, includes illustrative examples, and contains no fluff. Every word contributes to conveying the tool's purpose.

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 is a simple getter with no parameters and no output schema, the description provides a good list of returned fields (name, email, phone, address, timezone, settings) but leaves room for ambiguity with 'etc.'. It does not describe the return structure or whether all business settings are included, but it is reasonably complete for the tool's simplicity.

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 input schema has zero parameters, so the description has no parameter semantics to explain. Per the rubric, with 0 params the baseline is 4. The description adds context about the returned fields, which is helpful, though not directly about parameters.

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 verb 'obtiene' (gets) and the resource 'información del negocio del usuario autenticado' (business information of the authenticated user). It lists specific fields (name, email, phone, address, timezone, settings) which makes the purpose unambiguous and distinguishes it from siblings like gerent365_get_employee (employee data) and gerent365_get_profile (user profile).

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: to retrieve business information for the authenticated user. However, it provides no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. The context suggests it is the canonical getter for business data, but the description does not articulate this.

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