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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely new behavioral context beyond them: prices are net and exclude VAT, the value is per week, and implementation pricing is deliberately withheld until after the workshop — a business constraint an agent could not infer.

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 key payload (what is returned) is buried after an opening sentence of engagement-process framing that does not help an agent invoke the tool. The second sentence is dense but well organized, so the paragraph is padded rather than wasteful.

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 output schema, the description carries the burden of describing returns and does so explicitly (price, duration, deliverables, offer page). Nothing critical is missing for a single-optional-param read tool, though VAT/currency treatment could be stated neutrally rather than in prose.

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% and the enum is documented, so the baseline is 3. The description goes further by annotating each market with its currency (PL→PLN, CH→CHF, INTL→EUR) and clarifying that omitting the market returns all of them, which adds meaning beyond the bare enum list.

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 resource (the process workshop offer) and enumerates exactly what is returned: net price per week, duration, deliverables, and an offer page per market. It is unmistakable against the siblings (get_contact_options, get_page, list_pages, search_site), none of which touch workshop pricing.

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?

Usage is only implied: framing the workshop as 'how every JustAutomate engagement starts' and noting that implementation is quoted only after the workshop hints at when this tool applies. No explicit when-to-use, no named alternative, and no conditions telling the agent when to pick a sibling tool instead.

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