Read a booking's outcome history

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety bar is low; the description still adds real value with 'Corrections append rather than overwrite' and the scope/data-sensitivity disclosures. It does not mention pagination or result volume for an 'every outcome ever' read.

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?

Front-loads the core behavior in the first sentence, then layers operation/scope/workspace metadata compactly. Slightly boilerplate-heavy but every line carries actionable 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?

An output schema exists, so return values needn't be described; scopes, auth, and workspace resolution are covered. Only the absence of pagination/volume hints for a potentially unbounded history leaves a minor gap.

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 67% (id is undocumented, workspace params have descriptions), so the schema does part of the work. The description explains the workspaceId/workspaceSlug override against the environment-configured default, adding meaning the schema alone doesn't convey.

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?

States a specific verb and resource ('Read every outcome ever recorded on a booking, in order') and adds the append-only nuance. It is clearly distinguishable in intent, though it does not explicitly name the nearest sibling (luca_bookings_outcome_get) to contrast history-vs-current outcome.

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?

Provides operational context (required scopes, workspace override, idempotency not required) but gives no explicit when-to-use/when-not guidance versus outcome_get, outcome_record, or outcome_reasons_list. Usage is only implied by the 'history' framing.

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