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

The phrase 'Expression discarded' hints at a stateless evaluation, but there is no explanation of side effects, return values, error behavior, or what 'discarded' means. Since no annotations are provided, the description carries full responsibility and does not sufficiently disclose behavior.

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 but not effective; the single sentence introduces a purpose contradicted by the schema and omits essential operational details. Brevity is not helpful when it leaves the reader unable to determine valid inputs or expected outputs.

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 9 parameters, no output schema, and no annotations, yet the description only mentions arithmetic evaluation and discarding the expression. It does not explain how the listed parameters relate to the operation, what the tool returns, or when it should be invoked.

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 schema description, those descriptions are inconsistent with the stated arithmetic purpose and with each other (e.g., 'Git ref name', 'HTTPS URL to normalize or cite', 'City name for a public weather hint'). They add confusion rather than meaning, especially with no expression parameter present.

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 says 'Evaluate a+b style arithmetic' but none of the schema parameters represent an expression; parameters are unrelated strings like url, city, host, json, path, zone, query. This is misleading rather than clarifying the tool's actual purpose, and it does not distinguish it from the many sibling validation/check 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 given about when to use this tool versus the many sibling tools such as fetch-status, validate-json, normalize-url, or search-query-len. The description and parameter names imply a grab-bag of different checks with no criteria for selection.

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