List Newsletter Assets

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

Description adds context about reusable media and usage timing beyond readOnlyHint annotation. Does not contradict annotations and discloses nature of operation.

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?

Two sentences, no wasted words, front-loaded with purpose and usage context.

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?

Provides purpose and usage context but does not explain pagination or parameter usage. With output schema present, return values are covered, but parameter documentation gap remains.

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?

Description adds no information about parameters; schema has 50% coverage (only limit and cursor described). Without description help, agent lacks guidance on q filter or kind enum.

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?

Description uses specific verb 'List' and resource 'newsletter images and videos', clearly distinguishing from sibling tools like shipmail_register_newsletter_asset.

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?

Explicitly states to use before inserting already-uploaded media into a newsletter draft, providing clear context. Does not explicitly mention alternatives but implication is sufficient.

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