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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'lists artist records' and omits important traits like pagination, filtering, ordering, response profiles, or sensitive data handling. This is a significant gap for a listing tool.

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, focused sentence with no redundancy. It is appropriately concise, though it could have included more context without becoming verbose. The front-loaded verb and resource make it immediately clear.

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 8 parameters, several of which control pagination, ordering, and sensitive data access, the one-line description is far from complete. It does not explain the tool's capabilities or how the parameters relate to its behavior. Even with an output schema, the description fails to provide sufficient context for effective use.

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 63%, above the 50% threshold, so baseline is 3. The description adds no parameter information beyond the schema, but the schema itself documents several parameters (order_by, response_profile, sensitive_access_purpose). The description does not compensate for the undocumented page, search, and per_page parameters.

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 the tool lists artist records for the current tenant, using a specific verb ('Lista') and resource ('registros de artista'). It distinguishes from sibling get_artist and other list_* tools by identifying the entity type.

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 gives no guidance on when to use this tool versus alternatives, such as get_artist for single records or other list tools. There is no mention of exclusions or preferred scenarios.

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