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

No annotations are provided, so the description carries the full burden, and it does disclose the calculation model (which cost components are subtracted) plus the exact set of returned metrics despite there being no output schema. For a stateless calculator this is the meaningful behavioral information. It still omits permission/auth context and any note about assumptions or defaults (e.g., what platform presets imply).

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?

A single dense sentence that is well front-loaded with the toolbox tag and the core purpose, followed by deductions and outputs. Every clause carries information; only the bracketed toolbox label is pure context padding.

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 8 parameters at 38% coverage, the description covers the return values well but leaves real gaps: the meaning of the tax enum values ('0','1','5'), whether platform presets override user-supplied commission, and the units/role of qty and cost. It is adequate to select the tool but not fully sufficient to invoke it confidently for all parameters.

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 only 38%, and the four undescribed parameters (qty, cost, price, platform) are never clarified in the description, so the description does not compensate for the coverage gap. It does tie the deduction categories to parameters (運費→ship, 分潤→commission, 營業稅→tax, platform 抽成→platform, 目標毛利→target), but adds no unit or semantics beyond the schema's own '每單運費' and '%' notes.

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 a specific verb+resource: a profit/pricing estimator (試算) for group-buy and influencer direct-sale orders, and enumerates the deductions (platform commission, payment fees, shipping, revenue share, business tax) and the returned figures (net profit, gross margin, break-even price, target-margin price). This is far more specific than the bare tool name. It does not, however, explicitly differentiate itself from adjacent siblings such as creator__platform_fees or creator__calc_creator_withholding.

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 or when-not-to-use guidance, and no alternative tool is named. The closest sibling, creator__platform_fees, could plausibly be confused with this one (one looks up fee rates, this one computes profit), but the description never resolves that choice for the agent. Usage is only implied by the topic.

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