Octura Solutions Site Tools

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

With no annotations, the description must carry the behavioral transparency burden. It indicates the output (source deductions) but does not disclose return format, assumptions about tax rates, or whether it is a pure calculation with no side effects. This is a partial but incomplete disclosure.

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 extremely terse but also a fragment without a verb, making it under-specified rather than efficiently concise. The structure is a list of deduction types rather than a full sentence, which weakens clarity.

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 five parameters, no output schema, and no annotations, this one-phrase description is highly incomplete. It does not address calculation basis, return values, or how exemptions work, making it inadequate for correct tool selection and invocation.

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 does not explain any of the five parameters. Terms like cppExempt, eiExempt, and grossPerPeriod are left undefined, leaving the agent to infer meaning solely from names and schemas, which is insufficient.

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, 'CPP, EI, and income tax source deductions,' clearly identifies the tool's scope and differentiates it from sibling sales-tax calculators. However, it is a noun phrase lacking an explicit verb like 'calculates,' so it is clear but not perfectly stated.

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 use for Canadian payroll deductions, but it does not explicitly state when to use this tool versus alternatives or provide any exclusions. The context is implied by the specific deduction types mentioned.

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

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It says nothing about how the tool behaves, such as the add/extract direction, whether it returns a tax breakdown, or how amounts are treated. The description is purely descriptive of the subject matter, offering zero transparency about the tool's operation.

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 sentence with zero fluff, making it highly concise and front-loaded. However, it is a noun phrase rather than a complete sentence, and the extreme brevity means it sacrifices substance. For a tool with 3 parameters and a critical mode switch, this is slightly too under-specified, but as a measure of conciseness it earns a 4.

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's complexity (add/extract modes, province-specific rates, no output schema, no annotations), the description is completely inadequate. It fails to mention how the calculator works, what output to expect, or how parameters interact. This is far below the minimum viable completeness for a tool of this nature.

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 only 33% (only 'amount' has a description). The description fails to compensate for this gap; it doesn't explain the 'direction' parameter or the 'province' parameter in a meaningful way. It mentions tax types, which are not parameters, and 'all provinces', which loosely aligns with the province enum but adds no practical guidance. This minimal addition prevents a score of 1 but it is still insufficient.

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 'GST, HST, PST, and QST for all provinces' clearly indicates the tool's domain (Canadian sales tax), but it lacks an explicit verb like 'calculates' or 'computes'. It is more of a tagline than a clear functional statement, and while it distinguishes from US/EU sibling tools by mentioning Canadian tax types, it doesn't fully state what the tool does.

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 explicit guidance on when to use this tool versus alternatives like us-sales-tax-calculator or eu-vat-calculator. The description implies a Canadian context but does not provide when/when-not conditions or mention other tools. This leaves the agent to infer usage from the title and scope.

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

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

With no annotations, the description carries the full burden, but it only states the goal. It does not disclose assumptions (e.g., constant demand), the output format, or that it is a pure calculation. No side effects are relevant, but the lack of detail is a 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, tight sentence with no fluff. It earns its place by stating the core purpose, though it is terse and lacks additional structure.

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 simple calculator, the description is minimal and insufficient: no output description, no parameter semantics, and no behavioral context. It meets the bare minimum but doesn't fully equip an agent to use the tool 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?

The schema has 0% description coverage, and the description adds no parameter explanations. The parameter names (orderCost, annualDemand, holdingCostPerUnit) suggest their meaning, but the description doesn't clarify units or definitions, leaving room for misinterpretation.

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 states the tool's output – optimal order quantity – and its objective (minimize cost). This clearly identifies the EOQ calculation and distinguishes it from sibling inventory calculators like reorder-point or safety-stock, though it lacks an explicit verb like 'calculate'.

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 the tool is used when an optimal order quantity is needed to minimize cost, but it provides no explicit guidance on when to choose this over other inventory calculators, nor any exclusions or alternatives.

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

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

No annotations are provided, so the description must disclose behavioral traits. It only says the tool 'scores' a shortlist, but offers no detail on how scoring works, what output to expect, or any important side effects. This is minimal and insufficient for a tool with 8 parameters.

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 with no wasted words, making it concise. However, it is under-specified for the tool's complexity, offering only a bare statement of function without structure or additional useful context.

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?

The tool has 8 parameters, no output schema, and no annotations. The description is just one sentence and fails to provide adequate context about inputs, outputs, or behavior. This is completely inadequate for a tool of this complexity.

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 provides no explanation of any of the 8 parameters (size, needs, budget, region, industry, incumbent, deployment, customization). The enum values may be self-explanatory to some degree, but the description does nothing to compensate for the lack of parameter documentation.

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+resource: 'Score your best-fit ERP shortlist across 10 systems.' It clearly states the tool evaluates ERP options, which distinguishes it from sibling calculators and odoo-specific 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?

No explicit guidance on when to use this tool vs alternatives. The description only implies its purpose for ERP selection but does not mention when not to use it or how it compares to other selection tools.

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

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

With no annotations provided, the description must disclose behavioral traits but only mentions 'VAT rates' and 'VIES validation'. It does not explain the direction parameter's effect, whether external calls are involved for VIES, rounding behavior, or rate source reliability.

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 concise sentence with no redundancy, and it front-loads the two main features. However, its brevity crosses into under-specification, though for conciseness alone it earns a high score.

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 no output schema, no annotations, and a three-parameter tool with dual-mode direction, the description is critically incomplete. It fails to explain return values, how to use direction, or validation semantics, leaving the agent without essential operational context.

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 schema descriptions cover amount and country (67% coverage), but the 'direction' enum lacks description. The tool description adds no parameter clarification, leaving the distinction between 'add' and 'extract' unexplained, which is a meaningful gap.

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 'VAT rates by country plus VIES validation' mentions two features but fails to explicitly state the tool's primary calculation capability (adding/extracting VAT). It is not a tautology but is vague compared to the title 'EU VAT Calculator & Validator', which implies calculation is core.

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 on when to use this tool versus sibling calculators (e.g., Canadian or US sales tax tools). The description does not specify target users, use cases, or exclusions, leaving the agent without decision criteria.

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

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

With no annotations available, the description carries the full burden of behavioral disclosure. It does not explain how the calculation is performed, what inputs are required, what the output represents, or any limitations. This is a significant gap for a calculator tool.

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 extremely short and contains no redundant wording, but it is more of a fragment than a complete sentence. While it is concise, it lacks substance and does not earn its place as sufficient guidance.

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 simple two-parameter calculator, the description is incomplete. It does not mention the expected output format, the formula, or the units of the result. Without an output schema, more effort is required to explain the return value, which the description fails to do.

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 0% description coverage, and the description itself does not mention or explain any parameters. The parameter names ('avgInventoryValue', 'carryingRatePercent') are self-explanatory, but the description adds no additional semantic context, so it fails to compensate for the schema gap.

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 'Annual cost of holding inventory' clearly identifies the tool's output, implying that it calculates the annual carrying cost of inventory. The resource is specific, but it lacks an explicit verb like 'calculates' and doesn't explicitly differentiate from sibling calculators in the description text, though the name does.

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 is provided on when to use this tool versus alternatives such as inventory-turnover-calculator or economic-order-quantity-calculator. The description only states the purpose without any contextual usage hints or exclusions.

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

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

With no annotations provided, the description carries the full burden. It only states the outputs and gives no detail on inputs, formula assumptions, units, or any behavioral traits. The agent receives no information about how the calculation is performed or what is required.

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 extremely short and under-specified. While it is concise in word count, it is not appropriately sized because it omits essential information, making it a fragment rather than a structured statement.

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?

The tool is a calculator with two parameters, no output schema, and no annotations, yet the description only states the output concept. It fails to explain parameter meaning, calculation logic, or any other context needed to invoke the tool 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 description coverage is 0%, and the description does not mention the parameters at all. Although parameter names are self-descriptive, the description adds no meaning beyond the schema, so the agent cannot understand how inputs relate to outputs.

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 states the tool computes 'Turnover ratio and days of inventory,' which clearly identifies the resource and output metrics. It distinguishes from sibling calculators by focusing specifically on inventory turnover, though it lacks an explicit verb like 'calculate.'

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 is provided on when to use this tool versus alternatives, prerequisites, or typical scenarios. The description simply states outputs without any context for selection.

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

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

With no annotations available, the description must disclose the tool's behavior and side effects. It only notes that the cost includes freight and duty, but does not describe the calculation formula, default handling, output format, or any assumptions about currency or units. This is a notable transparency 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 very short and front-loaded, with no redundant wording. However, it is a fragment lacking a main verb and omits essential context, making it terse rather than effectively concise.

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 complexity of 6 unannotated parameters, no output schema, and no annotation support, the description is incomplete. It fails to state the cost formula, whether inputs are required or optional, what the computed result represents aside from 'per-unit cost,' and how to validate the result. This is insufficient for confident tool selection and invocation.

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 schema has zero description coverage for its 6 numeric parameters, and the tool description only mentions freight and duty. It does not clarify the role of quantity, insurance, otherFees, productCost, or customsDuty, nor how they combine to produce per-unit cost. The description provides minimal added meaning beyond parameter names.

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 what the tool computes: a per-unit cost that includes freight and duty. It distinguishes this from sibling calculators by focusing on landed cost, but it does not use a verb like 'Calculates' or 'Estimates,' so it falls short of the most explicit standard.

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 is provided on when to choose this tool over other cost calculators or how to interpret its results in an import workflow. There are no exclusions or references to alternatives, leaving the agent without contextual direction.

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

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the core conversion function without revealing any details about input constraints, mode behavior, defaults, or what the return values represent. The tool's behavior beyond the one-liner is entirely unspecified.

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 concise sentence with no filler or redundant information. It is front-loaded with the core purpose and is appropriately sized for a simple calculation tool.

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 has four parameters, no output schema, and no annotations, a one-sentence description is insufficient. It does not explain the two modes ('fromPrice' vs 'fromMargin'), how to use the target margin, or what the output format is. The description is minimal to the point of incompleteness for effective tool selection and invocation.

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 description mentions none of the four parameters (cost, mode, price, targetMarginPercent) and schema coverage is 0%. The schema provides defaults and ranges but no semantic meaning. The description does nothing to explain how parameters map to the conversion logic, leaving the agent to guess.

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: 'Convert between margin, markup, and price.' This is a specific verb and resource, and the topic distinguishes it from sibling calculators focused on sales tax, payroll, or inventory. However, it lacks an explicit statement of scope or output, so it doesn't fully differentiate beyond the title.

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 provides no guidance on when to use this tool versus alternatives. There is no mention of specific scenarios, prerequisites, or exclusions. The sibling tools are not referenced, leaving the agent to infer applicability from the name alone.

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

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

No annotations are provided, so the description must disclose behavioral traits. It only states a generic 'Find' action, giving no insight into what the tool returns (e.g., a ranked list, recommendations, or a summary), whether it uses the input parameters, or any limitations. This is insufficient for a tool with no annotation coverage.

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 sentence, but it is under-specified rather than concise. It does not use the available space to convey necessary information. The structure lacks any differentiation from the tool name and does not earn its place, as it merely restates the obvious.

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?

With three parameters, no output schema, no annotations, and 23 sibling tools, this description is completely inadequate. It provides no details on return values, how the tool works, or when to choose it over alternatives. The tool is effectively a black box with only a vague one-liner.

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 does not compensate by explaining any of the three parameters (needs, users, businessType). The schema provides enums and defaults but no semantic meaning. The description's single sentence contains zero parameter information, making it impossible for an agent to understand how inputs affect recommendations.

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 'Find the Odoo apps your business needs' clearly states the tool's purpose: recommending Odoo apps based on business needs. It uses a specific verb ('Find') and resource ('Odoo apps'), but does not distinguish it from sibling tools like erp-selection-tool or odoo-conf-tuner, so it falls short of a 5.

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 on when to use this tool versus alternatives. The description implies a general use case (finding apps for business needs) but provides no context, prerequisites, or exclusions. It does not mention how it differs from other Odoo-related tools or calculators.

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

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

With no annotations provided, the description carries the full burden for behavioral disclosure. 'Tune' implies a mutating operation, but there is no mention of side effects, file persistence, whether the config file must exist, or what the output looks like. This lack of transparency is risky for an agent invoking the tool.

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 with no wasted words. It directly states the core action and target. However, it is almost too terse given the tool's complexity, but for pure conciseness and structure, it is efficient.

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?

The tool has 7 parameters, no output schema, and no annotations, yet the description is only 7 words. It provides no information about return values, default behavior, parameter interactions, or the overall effect of tuning. This is far from complete for an agent to select and invoke 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 0%, and the description adds no parameter-level meaning. The description mentions 'workers and memory limits' but does not connect them to the 7 parameters, such as cpuCores or totalRamMb. While some parameter names are self-descriptive, the description fails to explain how they influence tuning.

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 the specific verb 'Tune' with a clear resource, 'odoo.conf', and explicitly names the targets: 'workers and memory limits'. This clearly distinguishes it from sibling tools like calculators or selectors, which serve different purposes.

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 on when to use this tool versus alternatives. The description does not mention prerequisites, scenarios, or tools to prefer instead, leaving usage entirely implicit. It merely states an action without context.

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

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

There are no annotations and the description offers no behavioral details such as factors considered, assumptions, or output format. It only implies a cost calculation without disclosing scope or limitations.

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 concise sentence with no wasted words, earning high marks for brevity. However, it sacrifices necessary detail for conciseness.

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?

With six parameters and no output schema or annotations, the minimal description is inadequate. It doesn't explain inputs, methodology, or what the cost estimate includes.

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 does not explain any of the six parameters. Enum values are left to the agent to infer from the schema.

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 estimates EDI integration cost within Odoo, using a specific verb and resource. It is distinguishable from sibling calculators by focusing on EDI, though it doesn't explicitly mention alternatives.

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 is provided about when to use this tool versus similar Odoo calculators like odoo-implementation-cost-calculator. The description only states the function without context.

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

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

No annotations are provided, and the description offers no behavioral details—no mention of input requirements, output format, accuracy, assumptions, or any side effects. The single sentence is merely a restatement of the title with no added transparency.

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, making it concise and front-loaded. However, it is so minimal that it approaches tautology, and it is not appropriately sized for a tool with 4 parameters and no annotations. It lacks the substance needed to be considered well-structured.

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's complexity (4 parameters, no output schema, no annotations) and the many sibling Odoo calculators, the description is severely incomplete. It provides no context about how estimates are calculated, what inputs are important, or how results should be interpreted. An agent cannot reliably select or invoke this tool based on this description alone.

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 schema has 4 parameters with 0% description coverage. The description does not mention any of these parameters or explain how they influence the estimate. With such low schema coverage, the description needed to compensate but provides nothing.

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 function: 'Estimate your Odoo implementation budget.' It identifies a specific verb (estimate) and resource (implementation budget), and the title reinforces this. It distinguishes from sibling tools like migration or upgrade cost calculators by focusing on implementation.

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 is provided on when to use this tool versus alternatives such as odoo-migration-cost-calculator or odoo-upgrade-cost-calculator. The description does not mention scope, prerequisites, or exclusion criteria.

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

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

No annotations are supplied, so the description must carry the burden of behavioral disclosure. It only says 'Estimate the cost to migrate,' leaving unclear what the estimate includes, how inputs affect the result, or any assumptions/limitations. This is insufficient for a calculator with many parameters.

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 with no filler. Every word earns its place, making it highly concise and well-structured, even though it sacrifices completeness.

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 complexity of 10 parameters, no annotations, and no output schema, the one-sentence description is far from complete. It does not explain what factors matter, what the output looks like, or how it differs from sibling Odoo calculators.

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 10 input parameters. Parameter names/enums (e.g., source, volume, quality) offer some inherent hints, but the description itself contributes zero semantic value beyond the schema.

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 identifies the tool with the verb 'Estimate' and a specific resource ('cost to migrate to Odoo'). However, it does not explicitly contrast with sibling calculators like odoo-implementation-cost-calculator or odoo-upgrade-cost-calculator, so sibling differentiation remains implicit.

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 is provided on when to use this tool versus the many similar Odoo cost calculators (implementation, upgrade, TCO). The description only states what the tool does, with no mention of appropriate scenarios or alternatives.

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

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the core purpose and does not mention any assumptions, side effects, or that this is a read-only calculation. It does not disclose that the tool likely uses a simple financial model or that results are estimates depending on inputs.

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, efficient sentence: 'Estimate payback and multi-year ROI of Odoo.' It is front-loaded and contains no fluff. However, it is arguably too terse, lacking important context, but as a concise summary it earns a high score.

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 calculator with four parameters and no output schema, the description is severely incomplete. It does not explain what inputs mean, what the output looks like, or how to interpret the results. There is no guidance on how the tool integrates with the sibling Odoo calculators. The description is a bare minimum that leaves the agent without enough context to use it effectively.

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 provides no information about the four parameters (odooAnnualCost, currentAnnualCost, implementationCost, annualEfficiencySavings). It does not explain whether costs are annual, monthly, or one-time, nor what the output represents. The agent receives no semantic value beyond the parameter names.

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 function: 'Estimate payback and multi-year ROI of Odoo.' The verb 'estimate' is specific, and the resource 'payback and multi-year ROI of Odoo' distinguishes it from sibling tools like cost calculators or TCO calculators. It is unambiguous about what the tool does.

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: when one needs to estimate ROI or payback for Odoo. However, it does not explicitly mention when not to use it or name alternatives such as the total-cost-of-ownership calculator. The context is clear but there are no exclusions or alternative references, so it is merely implied.

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

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

With no annotations, the description carries full burden for behavioral disclosure. It only says 'estimate,' implying approximate output, but does not mention whether the tool is read-only, how costs are calculated, or what output format to expect. This is minimal and insufficient for a tool with no other behavioral clues.

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, which is concise but under-specified for a tool with 7 parameters and no annotations. It sacrifices necessary detail for brevity, making it more underspecified than genuinely concise.

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's moderate complexity (7 parameters, no output schema, no annotations), a one-line description is grossly incomplete. It fails to explain parameter significance, calculation assumptions, or output structure, leaving the agent without enough context to invoke the tool confidently.

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 provides no information about any of the 7 parameters. The agent must rely entirely on self-explanatory parameter names and enums, which may not clearly convey semantics like 'appsBand' or 'workerChoice'.

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 estimates Odoo.sh hosting costs, which is a specific resource and action. It implicitly distinguishes from sibling calculators like implementation or TCO by focusing on hosting, though it does not explicitly name alternatives.

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 on when to use this tool versus the many other Odoo cost calculators. The description states only what it does, not when it should be chosen over alternatives, so the agent must infer usage from the name.

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

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

The description offers no insight into how the calculation works, what assumptions are made, or what the output contains. Since no annotations are provided, the description carries the full burden and fails to disclose behavioral traits.

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 with no redundant words. It efficiently conveys the tool's purpose, earning a top score for conciseness and structure.

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 no output schema and no annotations, the description is under-specified. It does not state whether savings are monetary, time-based, or estimated, nor how results are presented. This is insufficient for an agent to confidently invoke the tool.

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 description does not explain the parameters 'users' or 'selected', but the schema provides a default list and a description for 'selected', making its role clear. With 50% schema coverage, the parameters are partially self-explanatory, so this is adequate but not enhanced by the 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 states the tool shows savings from consolidating tools into Odoo, which clearly indicates the core purpose. However, the verb 'see' is less specific than 'calculate' or 'estimate', and it does not differentiate from sibling calculators like odoo-roi-calculator.

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 is provided on when to use this tool versus alternatives. There is no mention of prerequisites, suitable scenarios, or exclusions, so an agent must infer usage from the title alone.

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

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

With no annotations, the description carries the full burden of behavioral disclosure, but it discloses nothing. It does not mention what outputs are produced, how the calculation works, or any side effects or requirements, leaving the agent completely in the dark.

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, but it is under-specified rather than concise. It conveys minimal information and duplicates what the title already implies, so it does not effectively earn its place.

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?

This is a 6-parameter calculator with no output schema or annotations, yet the description provides almost no context. The complexity warrants significant explanation of inputs, outputs, and usage, and the current description is completely inadequate for an agent to use 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 description coverage is 0%, and the description adds no parameter semantics. The parameter names and enums provide some inherent meaning, but the description itself fails to explain how inputs relate to the model or what each option affects, so it does not compensate for the lack of schema documentation.

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 'Model the multi-year total cost of Odoo' clearly states a specific verb and resource, and the 'multi-year' and 'total cost' aspects help distinguish it from single-year or implementation-specific calculators. However, it does not explicitly reference any sibling alternatives or further scope, so it falls short of a 5.

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 on when to use this tool versus alternatives. The description provides no context, prerequisites, exclusions, or alternative tool references, so an agent has no basis for choosing it over the many other Odoo-related calculators.

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

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only states the purpose and gives no information about how the calculation works, what inputs it uses, whether it returns a single estimate or breakdown, or any limitations. This is a minimal statement with zero behavioral detail.

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, which is concise and front-loaded with the core purpose. No unnecessary words are present. While it might be too brief for some uses, from a pure conciseness standpoint it earns its place.

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 six optional parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain what factors influence the cost estimate, what the output looks like, or how it relates to other Odoo calculators. An agent cannot confidently invoke this tool based on the provided context.

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 parameter meaning. It does not mention dbSize, downtime, customModules, or any of the six parameters, leaving the enums and parameter names as the only semantic hints. With this low coverage, the description needs to compensate but completely fails to do so.

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 "Budget an Odoo version upgrade" clearly states a specific verb (budget) and resource (Odoo version upgrade). However, it does not differentiate from the closely named sibling 'odoo-migration-cost-calculator', so it misses the distinguishing detail between upgrade and migration costing.

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 is provided on when to use this tool versus alternatives such as odoo-migration-cost-calculator or odoo-implementation-cost-calculator. The description only restates the purpose without any context or exclusions, leaving the agent to guess which calculator fits the scenario.

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

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states a definition, not what the tool does, what inputs it expects, what outputs it produces, or whether it is a pure calculation (no side effects). The description is not misleading, but it is nearly devoid of behavioral information.

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, concise phrase without fluff, which is structurally efficient. However, it is under-specified rather than appropriately concise—the brevity limits its usefulness. It is more informative than a pure tautology but still too sparse to be considered well-crafted.

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 5-parameter calculator with no annotations and no output schema, this description is severely incomplete. It does not explain the OEE formula, input definitions, output format, or usage scenarios. The agent cannot correctly select and invoke the tool based on this description alone.

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 does not explain any of the five parameters. The parameter names (e.g., goodUnits, totalUnits, downtimeMin) are somewhat self-explanatory, and defaults provide hints, but the description adds no meaning. The tool description wholly fails to compensate for the lack of schema documentation.

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 'Overall Equipment Effectiveness for production' clearly identifies the tool's domain and metric, distinguishing it from sibling calculators. While it lacks an explicit verb like 'calculate', the name 'oee-calculator' and title 'OEE Calculator' make the action implicit. It is more specific than a tautology, giving context that this is a production-related OEE 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?

The usage is implied by the tool name and description—an OEE calculator is used for manufacturing efficiency calculations—but there is no explicit guidance on when to choose this tool over alternatives. No exclusions or prerequisites are mentioned, so the agent must infer applicability from the sibling context.

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

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only offers a short phrase that doesn't explain what the tool computes, what inputs it uses, what outputs are produced, or any side effects. This is a significant gap for a calculator tool.

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 extremely concise but under-specified. It's a single short phrase that doesn't earn its place due to lack of substantive information. Like the 'Process' example, this is under-specification rather than effective conciseness.

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?

The tool has 3 parameters, no output schema, and no annotations. The description fails to explain the tool's function, parameter meanings, or expected output. It is completely inadequate for an agent to select and invoke this tool 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 description coverage is 0%, so the description must compensate. It mentions 'safety stock' but doesn't explain the other parameters (leadTimeDays, avgDailyUsage) or how they relate. The description adds almost no meaningful parameter semantics.

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 'When to reorder, with safety stock' gives a vague hint about the tool's purpose but lacks a clear verb and resource. It doesn't explicitly state that it calculates a reorder point, nor does it distinguish itself from the sibling 'safety-stock-calculator'.

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 provides no guidance on when to use this tool versus alternatives such as safety-stock-calculator or economic-order-quantity-calculator. There is no mention of context, prerequisites, or exclusions.

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

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

No annotations are present, so the description must carry the burden of disclosing behavior. It does not mention that this is a pure calculation, what output it returns, what formula or assumptions it uses, or whether it has side effects. The phrase 'buffer stock for demand and lead-time swings' gives subject matter context but not behavioral transparency beyond the name.

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 one-sentence description is short but under-specified; it is a fragment rather than a well-structured description. Conciseness is not valuable when key information about inputs, outputs, and usage is missing.

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?

With four undocumented numeric parameters, no output schema, no annotations, and only a seven-word description, the tool is not adequately explained. An AI agent would not know the calculation formula, the meaning of the parameters, or the returned value, making the description incomplete for a calculator of this complexity.

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 descriptions cover 0% of the parameters, and the description does not explain avgDailyUsage, maxDailyUsage, avgLeadTimeDays, or maxLeadTimeDays. It vaguely references demand and lead-time swings but fails to explain the max-vs-average distinction or how each parameter participates in the calculation, so it adds almost no semantic value.

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 'Buffer stock for demand and lead-time swings' identifies the tool's domain and inputs (demand, lead time) but is a noun phrase rather than an explicit action statement. It conveys safety-stock calculation, though it doesn't clearly distinguish it from the sibling reorder-point-calculator or explain what the computed buffer stock is used for.

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 related calculators such as reorder-point-calculator or economic-order-quantity-calculator. The description only hints at demand and lead-time variability, but no explicit when-to-use/when-not-to-use or alternative recommendations are provided.

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

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

Without annotations, the description carries the full burden of behavioral disclosure. It only states coverage and does not explain how calculations are performed, whether it returns a rate or amount, or the meaning of 'add' vs 'extract' modes. The tool's behavior remains largely opaque.

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 with no waste, but it is under-specified. While it does convey geographic scope, it omits essential details, making it less useful than a more complete but still concise description would be.

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 calculator with 3 parameters, no output schema, and no annotations, the description is starkly incomplete. It does not explain return values, usage modes, or any edge cases (e.g., states with no sales tax), leaving the agent without enough context to invoke the tool 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 67% (state and amount have descriptions, direction does not). The description adds no parameter information at all, failing to clarify the ambiguous 'direction' parameter, which is crucial for understanding how to use the tool. The description does not compensate for the gap.

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 identifies the resource (US sales tax) and its geographic scope (all 50 states and DC), which distinguishes it from the Canadian and EU tax calculators. However, it lacks an explicit action verb like 'calculate' or 'compute', relying on the title's 'Calculator' to imply the purpose.

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 gives no indication of when to use this tool over alternatives, nor does it mention any exclusions or prerequisites. With sibling calculators for other countries, explicit guidance about using this only for US states would be helpful, but none is provided.

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

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only states a high-level outcome without explaining how sales and transactions are used, what thresholds apply, or what the output looks like. Additionally, the description says 'where' but the schema has a 'state' parameter, creating ambiguity about whether it checks one state or all states.

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, clear sentence with no filler or redundant information. It is front-loaded and immediately communicates the tool's purpose, making it highly concise and well-structured.

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?

The tool lacks an output schema and annotations, so the description must provide sufficient context. It fails to mention the calculation logic, thresholds, return format, or whether the tool handles a single state or all states. For a tool dealing with complex economic nexus rules, this level of detail is inadequate.

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 provides detailed descriptions for all three parameters (sales, state, transactions), achieving 100% coverage. The tool description adds no additional parameter semantics, so the baseline score of 3 is appropriate.

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: to determine where US sales tax must be collected. The verb 'see' and resource 'where you must collect US sales tax' are specific enough to distinguish it from siblings like us-sales-tax-calculator, though it doesn't explicitly say 'economic nexus' or name the alternative.

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 is provided on when to use this tool versus alternatives such as us-sales-tax-calculator. There is no mention of prerequisites, exclusions, or scenarios where a different tool would be more appropriate.

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