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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), but the description adds genuinely non-inferable facts: the call is free, the series quota is 3 sheets total, and a new sheet costs 21 credits for a person or 10 for an animal/mascot. It does not mention pagination or edge cases like an empty sheet list.

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-loaded with the verb and resource, then layers in useful payload details. The single long sentence is slightly dense and mixes return-shape, pricing, and usage-sequencing into one breath, but nothing is wasted.

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?

There is no output schema, and the description compensates well by enumerating the returned structure (images with id, view, url; which sheet and image are chosen; remaining quota). Combined with pricing and the free-call note, an agent has everything needed to call it and relay results.

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 single parameter is already documented as 'A series id from autoshort_list_series.', so the description carries no additional parameter detail. Baseline 3 applies when the schema does all the work.

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 the character sheets of one of your series') and immediately defines what a sheet is (a set of AI images of one fictional character). It also names the sibling it precedes (autoshort_create_character_sheet), so the agent can distinguish it from create/select operations without opening a schema.

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?

Gives clear sequencing guidance: 'Use this before autoshort_create_character_sheet and tell the user the price.' Also flags 'Free', which helps the agent decide when to call it. No explicit when-not condition is stated, so it falls short of a 5.

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