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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is clear. The description adds value by noting pagination and the specific return fields (date, artist, venue, track list), which are not in the input schema. This provides behavioral context beyond annotations.

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 a single sentence that is front-loaded with the action and resource. Every word contributes to purpose and usage. No redundant or extraneous 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?

For a simple two-parameter tool with a rich output schema and comprehensive annotations, the description covers the core purpose, key parameter, pagination, and return fields. The only gap is the missing documentation of the p parameter, but overall it is sufficiently complete for an agent to use correctly.

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 clearly describes the required parameter user_id and implies pagination via 'paginated list', but the optional parameter p (presumably page number) is not explicitly documented. The description adds some meaning but is incomplete.

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 clearly states 'Fetch paginated list of concerts a user has marked as attended, by user_id'. The verb 'Fetch' and resource 'concerts a user attended' are specific, and the tool is easily distinguished from siblings like 'user' (general user info) or 'setlist' (single setlist).

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 implicitly indicates usage via the parameter user_id but does not provide explicit guidance on when to use this tool versus alternatives like 'user' or 'setlist_search'. No exclusions or counter-indications are mentioned.

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