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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing: it doesn't say whether the call is a read or a generation, what the output looks like, or whether the "workflow" is returned or executed. The "30-day support promise" and "ships as a full prompt kit" are commercial claims, not behavioral traits an agent can act on.

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?

It is short but not efficient: "AI-powered," "Instantly," "no prompt engineering needed," and the 30-day support promise consume most of the text without informing invocation. The one functional fragment (cost formula tool workflow) is buried inside sales framing rather than front-loaded.

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 annotations, no output schema, and only one loosely documented parameter, the description needed to explain what the tool returns and how to call it. Instead it delivers a product pitch, leaving an agent unable to predict the result of a call in a crowded family of cost-* and formula-* siblings.

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?

There is a single optional parameter (query) with 100% schema description coverage, so the schema already explains it as an optional scoping query. The description adds no meaning beyond that, which makes the documented baseline of 3 appropriate.

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 it will "generate a ready-to-use cost formula tool workflow," which mostly restates the tool name rather than explaining what the tool actually does. It never distinguishes cost-formula-tool from the many adjacent siblings (cost-analyze-tool, cost-board-tool, cost-diag-tool, cost-tpl-tool), so an agent cannot tell what this one produces that the others do not.

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?

There is no when-to-use guidance, no prerequisite, and no named alternative. The only selection-adjacent sentence is marketing copy ("no prompt engineering needed"), which does not tell an agent under what conditions to pick this tool over its siblings.

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