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

No annotations are provided, and the description does not disclose any side effects, side effects, or operational behavior. The phrase 'Expression discarded' is vague and does not clarify what happens to inputs or outputs.

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 concise (one sentence) but fails to be front-loaded with relevant information. The brevity is not a strength because the content is misleading, so it does not effectively convey the tool's function.

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?

Given the mismatch between the description and parameters, the description is fundamentally incomplete. It does not explain what the tool actually does, what the parameters mean, or what the output is, leaving an agent unable to use the tool 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 parameter descriptions exist for all 9 parameters, they are nonsensical and inconsistent with the tool's stated purpose (e.g., 'Git ref name; discarded after shape check' for a calc tool). The descriptions do not add meaningful semantic value and actively confuse rather than clarify.

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 'Evaluate a+b style arithmetic' but the actual parameters (ref, url, city, feed, host, json, path, zone, query) are entirely unrelated to arithmetic. The description misrepresents the tool's purpose, making it misleading.

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 any alternative. The description offers no context or conditions for appropriate usage.

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