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

Annotations already declare readOnlyHint=true, so the safety bar is partly cleared, but the description adds a meaningful boundary beyond the annotation: 'this server never issues refunds.' That is a real capability constraint an agent needs, not a restatement. It stops short of pagination behavior, though the schema covers page/page_size.

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 purpose, follows with the read-only boundary, and closes with the upstream endpoint. Three compact clauses with no filler, each carrying distinct 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?

With no output schema, the description compensates by enumerating the returned fields, and the read-only plus endpoint notes round out the picture an agent needs to call this correctly. Nothing material is left unspecified for a simple read list tool.

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% and all four parameters are documented in the schema, so the baseline of 3 applies. The description adds no parameter-level detail (e.g. account_slug fallback or paging semantics) beyond what the schema already states.

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 (List) and resource (refunds) scoped to an event, and enumerates the returned fields (amount, created_at, manual flag, registration). An agent can distinguish this from sibling list tools like tito_list_registrations or tito_list_activities 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?

Usage is implied by the 'recorded for an event' scoping, and there is no competing refund tool among siblings, so no alternative needs routing. However, it never states when an agent should reach for this versus adjacent list endpoints, nor any prerequisite conditions, so the guidance is only implicit.

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