camelot_market_sizing_calculator

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

The description adds 'Local browser processing,' which communicates a meaningful behavioral trait beyond the annotations: computations are performed locally without server-side side effects. This complements the idempotent and non-destructive hints, though it does not detail the exact return behavior, which is covered by the output schema.

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 compact and front-loaded with the core purpose, followed by useful processing-context and canonical URL. It earns its place, though the 'Market Sizing Calculator:' prefix is slightly redundant with the tool name and there is a minor punctuation issue ('models..').

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 a simple deterministic calculator with fully documented parameters, defaults, and an output schema. The description adds processing-location context and a canonical reference. Nothing essential for invoking it correctly is missing.

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 100%, so the parameter descriptions already carry the semantic load. The description's mention of top-down and bottom-up models gives methodological context but does not add parameter-specific detail beyond the schema.

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 ('Estimate') and a specific resource ('TAM, SAM, and SOM market sizes'), and names two methodologies ('top-down and bottom-up models'). This clearly differentiates the tool from sibling calculators focused on pricing, LTV/CAC, or other financial metrics.

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 gives clear context for when to use the tool: whenever a market sizing estimate is needed. It does not explicitly name alternatives or exclusions, but the domain is obvious enough that an agent can select it appropriately.

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