snapchat_get_creatives

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

Annotations already indicate readOnlyHint and destructiveHint. The description adds the caching behavior (5-minute cache), which is beyond what annotations provide. No contradictions; the description aligns with a read-only 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?

The description is extremely concise with two sentences. Every word is necessary and front-loaded: the action and the important caching note. No redundant 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?

Given the presence of an output schema, the description does not need to detail return values. It covers the essential action and caching behavior. A minor enhancement could mention that it returns all creatives for the account, but it is already fairly complete for a simple 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?

The description does not explain the required parameter ad_account_id. Although the input schema has a description for it, the context indicates schema description coverage is 0%, meaning the description must compensate. Failing to mention the parameter leaves the agent without guidance on what to provide.

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 it lists all creatives in the ad account. It uses a specific verb ('List') and resource ('creatives'), and it naturally distinguishes from sibling tools like snapchat_get_ads or snapchat_get_campaigns.

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 a clear use case (listing creatives) and adds the caching detail, which informs the agent about data freshness. However, it does not explicitly mention when not to use this tool or suggest alternatives, though the sibling tools cover different entities.

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