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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the description does not need to restate those. The description adds pricing and plan-inclusion context, which is useful but not behavioral. It does not disclose whether adding a duplicate member is silently ignored (idempotent) or whether the list must already exist, though idempotentHint partially covers that.

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 compact sentence that front-loads the action and resource, then adds pricing context. It is efficient and does not waste words, though the pricing detail could arguably be moved to a pricing reference.

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 mutation tool with no output schema, the description covers the core action and member identifier format. It lacks explicit confirmation of what 'id' refers to and does not mention error cases (e.g., nonexistent list, invalid slug/aid). The idempotentHint annotation covers duplicate behavior, but the description itself is thin on operational context.

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 only 33% (only 'context' has a description). The description adds meaning for 'members' by saying they are providers/APIs identified by slug or aid, which helps. However, 'id' is left undocumented in both schema and description; the description says 'one of your lists' but does not explicitly say id is the list id. This is a partial compensation for the coverage gap.

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 states a specific verb ('Add') and resource ('providers/APIs ... to one of your lists'), and clarifies the identifier types accepted (slug or aid). It is clear enough to distinguish from create_list and list_lists, though it does not explicitly name those siblings.

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 implies the use case: adding existing providers/APIs to a list. It does not explicitly state when to use this tool versus create_list, delete_list, or get_list, nor does it mention prerequisites like needing an existing list id. The pricing note is context but not usage guidance.

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