m2m_tax_matrix

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

No annotations provided, and the description fails to disclose behavioral traits such as read-only nature, error handling, currency assumptions, or whether reverse-charge mechanisms are supported. For a tax-related tool, this is a significant gap.

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 sentence without clear structure. While concise, it lacks the necessary detail for effective tool selection and invocation.

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 absence of output schema, annotations, and parameter descriptions, the tool is severely underdocumented. Critical information about return values, currency, tax calculation logic, and potential errors is missing.

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 description coverage is 0%, and the description adds no meaning to the four parameters. While parameter names are somewhat self-explanatory, no details are given about allowed values, format, or semantics (e.g., country codes, VAT ID validation).

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 'Cross-border EU VAT tax matrix for M2M transactions between AI agents' suggests the tool computes or returns VAT tax data, but the verb is implied and 'matrix' is ambiguous. It does not clearly state what action the tool performs (e.g., calculates, retrieves, or validates tax rates).

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?

No guidance on when to use this tool versus alternatives like 'm2m_predictive_rates' or 'm2m_global_tenders'. The description does not specify prerequisites, contexts, or exclusions.

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