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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the bar is lower. The description adds a genuinely useful caveat not available elsewhere: 'Values can lag slightly', telling the agent the numbers may be stale. It also discloses the composition of the usage breakdown, though it says nothing about error behavior for invalid quota ids.

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?

One front-loaded sentence names the core values, a second adds the staleness caveat, and the API path follows. Dense and mostly waste-free, though the raw endpoint path adds little for an agent that already has structured parameters.

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 return values, and it does so by naming available, available_number, total_size and the usage breakdown. Combined with the lag caveat, an agent has enough to call and interpret the result; only error/empty-quota handling is unaddressed.

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 event, quota_id, and the optional organizer are already documented in the schema. The description contributes only the endpoint template, which restates the path parameters rather than adding semantics like slug format or organizer-token behavior. Baseline 3 applies.

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 resource and question ('How much of a quota is left') and enumerates the key return fields, so an agent knows exactly what it retrieves. It is distinguishable from pretix_list_quotas in practice (availability vs. quota definitions) but never names that sibling to make the distinction explicit.

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 implied rather than stated: the endpoint path and field list make it clear this is the availability lookup for a specific quota id. There is no explicit guidance on when to prefer this over pretix_list_quotas or how to obtain the quota_id first, so the agent must infer the workflow.

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