calculate

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

Annotations are absent, so the description carries the full burden. It only says 'perform basic arithmetic calculations' and does not disclose edge-case behavior (e.g., division by zero), return format, or side effects. The stateless nature is implied but not stated, and error handling is completely unaddressed.

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 filler or redundant information. It is front-loaded and efficient, though very brief. No structural issues, but it could include a bit more detail without becoming verbose.

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 no output schema and no annotations, the description should at least mention the return type or behavior, but it does not. The tool is simple, but for full contextual completeness, the description should state that it returns the numeric result and possibly note error conditions like division by zero. As it stands, an agent is left to infer these details.

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%, with each parameter having a description (e.g., 'First number', 'Second number', 'The operation to perform'). The description adds no parameter-specific meaning beyond what the schema already provides, so the baseline score of 3 applies.

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 it performs basic arithmetic, which is clear but vague about the specific operations and operands. It doesn't explicitly mention that it takes two numbers or supports add/subtract/multiply/divide, and it doesn't distinguish itself from the sibling tool convert_temperature. The verb 'perform' and resource 'basic arithmetic calculations' are present, but the scope is under-specified.

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. The description does not mention any use cases, prerequisites, or exclusions, leaving the agent without context for selection. With siblings like convert_temperature, clearer differentiation would be helpful.

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