holded_get_taxes

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

With no annotations, the description carries the behavioral disclosure burden. The verb 'Obtiene' reasonably implies a read-only retrieval with no side effects, which is useful. However, it does not mention response format, pagination, rate limits, or authentication expectations, though the zero-parameter nature reduces the risk.

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 one short, focused sentence that states the action and the target resource with no filler. It is immediately parseable and front-loaded.

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 zero-parameter, no-output-schema tool, the description is largely complete: it identifies the resource as the configured taxes in Holded. It does not describe the shape of the returned list, but the simple nature of the tool makes this a minor gap rather than a blocking omission.

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 and the schema coverage is 100%, so there are no parameter meanings for the description to clarify. The baseline for zero-parameter tools is 4, and the description adds no unnecessary parameter detail.

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 uses a specific verb ('Obtiene') and a clear resource ('la lista de impuestos configurados en Holded'), making it evident that this tool returns the configured taxes. It is distinct enough from siblings like holded_get_vat_summary, though it does not explicitly differentiate itself from that related report tool.

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?

There is no guidance about when to use this tool versus alternatives such as holded_get_vat_summary or holded_list_documents. The description implies a simple retrieval operation but does not state any context, exclusions, or sibling comparisons.

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