calculate_profit_margin

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

No annotations provided, and the description does not disclose behavioral traits (e.g., read-only, no side effects). It merely states what it calculates, leaving safety and implications unaddressed.

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 concise sentences with no redundant information. The structure is efficient and immediately conveys the tool's purpose and a related resource.

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 financial calculation tool, the description is too brief. It fails to explain the return format clearly and does not account for the absence of annotations or output schema details, leaving the agent underinformed.

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 coverage is 100%, but the description adds no meaningful explanation for the parameters. The phrase 'Returns: {revenue, cost}' is misleading as revenue and cost are inputs, not outputs. No clarification on how they are used or interpreted.

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?

Description clearly states it calculates gross margin, net margin, and markup percentage. However, it does not differentiate from closely related siblings like calculate_markup_margin or calculate_break_even, and the mention of 'Returns: {revenue, cost}' is confusing.

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 explicit guidance on when to use this tool over alternatives. The reference to list_bundles for related calculators is vague and does not provide clear context for tool selection.

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