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

With no annotations, the description carries the full burden. It usefully discloses that unsupplied fees use an EXAMPLE default that must be verified—a key behavioral trait. However, it does not state that the tool is a pure calculation with no side effects, nor does it describe the output format or assumptions beyond the default warning.

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?

Two sentences with zero waste: the first states the core calculation, the second delivers a critical warning about defaults. Front-loaded and appropriately sized.

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?

For a tool with 8 parameters, 2 required, no output schema, and 0% schema description coverage, the description is insufficient. It lists the outputs but does not explain parameter meanings, constraints, or the shape/format of results. An agent would need to guess parameter semantics.

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 0%, so the description must define the 8 parameters. It only vaguely mentions 'fee value' without mapping to specific parameters like paymentFeeFixed or paymentFeePercent, and completely omits others such as monthlyFixedCosts and adCostPerSale. The description adds minimal meaning beyond parameter names.

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 clearly states the tool calculates specific profit metrics (profit per sale, margin, break-even price, maximum ad cost) for a product. It uses a precise verb+resource and is easily distinguished from the unrelated sibling tools (find_niches, generate_store_names, etc.).

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?

The description implies the tool is used for profitability analysis of a product, but provides no explicit guidance on when to use it versus alternatives or any prerequisites. It lacks exclusions or context about scenarios where the tool is appropriate.

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