Generate a prefilled URL without running calculation
| Name | Required | Description | Default |
|---|---|---|---|
| inputs | Yes | Input values for URL | |
| strict | No | If true, reject invalid or unknown input fields instead of dropping them | |
| calculator | Yes | Calculator slug |
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 notes that no calculation is run, but omits side effects, permissions, or whether the tool modifies any state. This is too little for a tool that could have side effects.
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 zero wasted words. It fully captures the essential behavior and distinction in a compact form.
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 three parameters (including a nested object) and no output schema. The description omits what the generated URL looks like, any encoding behavior, or return format, making it incomplete for a tool that produces a URL.
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 schema already describes all parameters. The description adds no extra parameter meaning, but the baseline of 3 is appropriate since the schema does the heavy lifting.
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 and resource ('Generate a prefilled URL') and adds a key qualifier ('without running calculation'). This clearly distinguishes it from sibling tools like 'calculate' and 'calculate_cas' that perform actual calculations.
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 phrase 'without running calculation' implies the tool is for when a calculation is not yet desired, offering clear context. However, it does not explicitly name alternative tools or state when to use this over them.
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.
The three calculation tools (calculate, calculate_cas, calculate_cas_headless) overlap significantly, with calculate_cas_headless being an explicit alias of calculate_cas. An agent may struggle to choose between them. Other session tools are distinct, but the calculation ambiguity lowers the score.
Most tools follow a verb_noun pattern (list_calculators, create_session, get_session_state). Minor deviations exist, especially calculate_cas_headless with the 'headless' modifier and calculate lacking a noun, but the overall pattern is predictable.
With 10 tools, the count is reasonable for a calculator service with session management and CAS features. However, the presence of an alias tool (calculate_cas_headless) makes the set slightly redundant, though not overstuffed.
The surface covers core calculation, CAS evaluation, prefilled URL generation, and session lifecycle (create, push, get state, close). Minor gaps exist, such as no explicit session listing, but most workflows can be completed without workarounds.