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

No annotations are present, and the description's phrase 'Expression discarded' is contradicted by the absence of any expression input. The tool's behavior, side effects, and return value are completely 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 extremely brief, but its brevity comes at the cost of clarity. It omits essential information about what the tool actually does and how the parameters are used, making the concise structure ineffective.

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 nine parameters, no output schema, no annotations, and no usage guidance, the tool definition leaves nearly every contextual detail unspecified. An agent cannot predict the tool's behavior or integrate 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?

Although every parameter has a description, none of those descriptions relate to arithmetic evaluation. Parameters like 'url', 'city', and 'feed' are described as discarded or checked, but their role in the tool is unclear, and there is no parameter that could hold the arithmetic expression mentioned in 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 claims to evaluate a+b arithmetic, but the input schema contains no expression parameter and instead lists nine unrelated string parameters with descriptions such as 'Git ref name' and 'City name'. This makes the tool's actual purpose impossible to discern, and it does not distinguish itself from the many sibling 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 guidance is provided on when to use calc-eval versus any alternative tool. The description and schema do not indicate what problem this tool solves, so an agent cannot determine appropriate usage.

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