Calculate profit

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds valuable context beyond annotations: 'Free to use; no Profitlee API token required' and details about returned metrics (per-unit fees, margins, monthly P&L). No contradictions with annotations.

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 two sentences: the first states the core action and scope, the second lists outputs and the free access. It is front-loaded, contains no redundant information, and every sentence contributes meaningful information.

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?

The tool is complex (26 parameters, 15 required, output schema present), but the description provides a concise high-level overview including platforms and return values. Schema covers all parameter details and the output schema explains return data, so the description is sufficiently complete without restating structured data.

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?

The input schema has 100% description coverage for all 26 parameters, so the schema already documents each parameter's meaning. The tool description does not add additional parameter-level detail beyond what the schema provides, but no compensation is needed because coverage is complete.

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 ecommerce profit for a single product across specified platforms (Amazon FBA/FBM, TikTok Shop FBT/self-fulfilled). It uses specific verbs and resources, and the sibling tools (list_scenarios, save_scenario, etc.) are scenario-management, making this calculator distinct.

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 when to use the tool (for profit calculation on supported marketplaces and modes) and explicitly mentions the output types, giving clear context. It does not name alternative tools or exclusions, but the sibling toolset is clearly different, so the usage context is well understood.

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