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

With no annotations, the description must carry the behavioral disclosure burden. It does add one useful behavior: 'Missing inputs fall back to their documented defaults.' However, it does not clarify whether the listed phrases are outputs, inputs, or calculation rules, nor does it describe the return format or any side effects. The lack of clarity around 'Deemed domiciled in Cyprus (1 = yes)' weakens the 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 short and front-loaded with the action, which is good. However, the 'calculator calculator' typo and the unlabeled semicolon list ('SDC rate on your dividends; Deemed domiciled in Cyprus...') make it feel disorganized and reduce clarity. It is concise but not as well structured as it could 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?

This tool has four parameters, no annotations, and no output schema, so the description needed to explain what the calculator returns and how to interpret the results. It only provides a default-fallback note and a confusing list of calculator-related phrases. An agent would not know whether the output is a rate, an amount, or a breakdown, making the description incomplete for reliable 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 100%, so the baseline is 3; all four parameters have descriptions, defaults, and ranges. The description adds some domain context by mentioning 'SDC rate', 'SDC on dividends', and 'SDC on interest', but it does not clearly map these concepts to specific parameters. It therefore provides only marginal 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 states a specific verb and resource: 'Run the Cyprus non-dom SDC calculator calculator'. The title and opening phrase make the tool's core purpose clear, even though the word 'calculator' is duplicated and the semicolon list is ambiguous. It does not explicitly distinguish the tool from its siblings like calculator_describe, so it misses the top score.

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 is given about when to use this tool versus alternatives such as calculator_describe or submit_enquiry. The only usage-related note is that missing inputs fall back to defaults, which is more of a behavioral hint than a usage guideline. An agent is left to infer the appropriate context.

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