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

The annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful context beyond annotations: free access, no authentication, rate limiting, and that margin is a percentage of selling price with no currency conversion. It does not specify rate-limit thresholds or detailed output behavior, but the annotations and output schema carry much of that burden.

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 four short, front-loaded sentences. The purpose is stated first, followed by the key margin and currency semantics, then authentication and rate-limit facts. Every sentence adds actionable information without filler.

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?

Given that an output schema exists and annotations are rich, the description covers the main gaps: what is calculated, how margin works, currency behavior, authentication, and rate limiting. It is largely complete for invocation, though it could better explain the six non-margin parameters; their self-documenting names mitigate this.

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 compensate. It valuably clarifies the most ambiguous parameter by defining margin as a percentage of selling price and notes that monetary values are currency-neutral. However, it leaves hoursOnSite, hourlyRate, editingHours, editingRate, gearTravelCost, and numPhotos without added semantic explanation, relying entirely on their names and schema ranges.

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 calculation verb and enumerates the exact outputs: session price, costs, profit, and per-photo price. This is clear and agent-readable. It does not explicitly distinguish this tool from sibling pricing tools such as agency_pricing or freelance_rate, so it falls short of a 5.

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 operational facts (free, no authentication, rate limited) but does not say when to use this tool versus alternatives like agency_pricing or freelance_rate. There is no when-not or alternative-selection guidance, so an agent must infer usage from the tool name alone.

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