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

Adds value beyond annotations: consent/legal requirements, potential API contract submission, and a returns-request_id + async follow-up model. One mild tension: the described endpoint 'PUT /subscription' implies idempotency while idempotentHint=false, which could mislead on retry behavior.

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?

Dense and front-loaded with the WRITE marker and core action first, then constraints, then return behavior. Every sentence carries information, though the run-on nature of the consent clause is slightly heavy.

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?

Without an output schema, the description still explains the return (request_id) and the follow-up tool, plus consent gating. Adequate for a mutation tool with rich annotations already covering safety hints.

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% (baseline 3), and the description adds the key constraint that each contact needs a mobile, email, or landline — a logical requirement not encoded in the schema's item properties. It also notes list names are comma-separated and must pre-exist.

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 (add) and resource (contacts to distribution lists), with the write nature flagged up front. Distinguishes itself from siblings like trumpia_update_subscription and trumpia_get_subscription by being the creation path.

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 preconditions: lists must already exist, each contact needs a valid identifier, and only consented contacts should be added (TCPA/CAN-SPAM/CTIA). It routes the agent to trumpia_get_request_report for async status, but doesn't explicitly contrast with trumpia_update_subscription for existing contacts.

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