es__query_sii_status

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

No annotations are provided, so the description must convey behavioral traits. It only states that the tool queries status, suggesting a read operation, but does not confirm idempotency, rate limits, or potential side effects. This lack of detail leaves the agent uncertain about the tool's safety.

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 short sentence, which is concise. However, it could be better structured with explicit guidance on parameter usage or a note about the batch_id origin. Given its brevity, it meets the minimum for clarity but wastes no 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?

Without an output schema, the description should hint at the return format or possible states. It does not. Additionally, the agent might wonder about error handling or how to interpret the response. The tool is simple, but the description omits context that would improve usability.

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 50% coverage: batch_id has a description, but record_type only has enum values. The description adds no additional context for either parameter, leaving the agent to infer meaning from the enum names and the brief tool description.

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 purpose: consulting SII batch status. It references the underlying AEAT operations (ConsultaFactInformadasEmitidas/Recibidas), which gives context. While it doesn't explicitly distinguish from siblings, the name and description make its function unique among the many es__ tools.

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 after submitting a batch via es__submit_sii_batch (since it mentions batch status and a batch_id parameter). However, it does not explicitly state when to use this tool versus alternatives (e.g., es__get_compliance_status), nor does it provide conditions or prerequisites.

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