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

With no annotations, the description carries the full burden and does well: it discloses the exact return shape (title, summary, last-updated date, source URL, JSON-LD), and states the default behavior when regulation is omitted (50 latest items). It does not mention auth or rate limits, which is a minor gap for a read-only lookup.

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?

Front-loaded with the purpose, then return shape, then usage and examples. Slightly padded by the long parenthetical list of regulations, which partially repeats content already conveyed by the return-shape sentence and the schema examples.

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?

No output schema exists, but the description adequately explains the returned fields and the default result size, plus working example calls. An agent has everything needed to invoke it correctly.

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%, so the baseline is 3, but the description adds concrete invocation examples ('{"country": "MEX", "regulation": "CFDI"}') that demonstrate the full-list vs. narrow-down distinction beyond the per-parameter schema docs.

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?

States a specific verb and resource ('Returns tax-and-regulatory compliance information') and enumerates the actual regulatory content for Colombia and Mexico. This is clearly distinguishable from siblings like get_articles or get_products.

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?

Explicitly states when to use it ('when the user asks about Siigo's compliance posture or specific regulations'). It does not name alternative tools or exclusion conditions, but no sibling overlaps meaningfully with this niche.

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