Return per-country features, default currency, and product positioning for a supported country (IN, AU, GB, US, CA, AE, SG, NZ).
| Name | Required | Description | Default |
|---|---|---|---|
| country | No | Single ISO country code. Omit for the full matrix. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It states the tool 'returns' data, which implies read-only behavior, but does not disclose details like behavior when the country parameter is omitted (though the schema covers that) or the return format. No contradictions.
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?
A single, front-loaded sentence that states the action and expected output with no filler. Every word 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?
For a simple 1-parameter tool with no output schema, the description covers the key purpose, return content, and supported countries. The parameter details and the option to omit for the full matrix are present in the schema, so the description is sufficiently complete.
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 100%: the parameter's description already explains 'Single ISO country code. Omit for the full matrix.' and the enum lists all values. The tool description adds the same country list, providing no additional 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 uses a specific verb ('Return') and identifies the exact resource: per-country features, default currency, and product positioning. It lists supported country codes, which distinguishes it from siblings like feature_search, list_features, and statutory_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?
The description clearly implies when to use this tool: when you need country-specific configuration data. It does not explicitly name alternatives or exclusions, but the country-scoped context differentiates it adequately from sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource: features, plans, competitors, country support, payroll engines, statutory rates, payment methods, and a free-text search across all of them. There is no overlap in purpose; even feature_search complements the list tools by handling ad-hoc queries.
Tool names are inconsistent: three use a 'list_' prefix (list_competitors, list_features, list_plans), while the rest are noun phrases like 'country_support', 'feature_search', 'local_payment_methods', 'payroll_capabilities', and 'statutory_rates'. There is no uniform verb_noun pattern, making names less predictable.
Eight tools is a well-scoped number for a product information server covering features, plans, competitors, countries, payroll, payments, and rates. Each tool has a clear role and the count is within the ideal range.
The tool surface covers all major categories one would expect for the HelloTime product domain: features, plans, competitor positioning, country-specific support, payroll engines, statutory rates, and payment methods. The feature_search tool further fills gaps by enabling cross-category queries, leaving no obvious dead ends.
