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

With no annotations, the description carries full responsibility for behavioral disclosure. It only says 'trigger' a refresh flow, without stating whether it is asynchronous, what side effects occur (e.g., data updates, rate limits), whether it is reversible, or what the return value is. The lack of any behavioral details beyond the action itself is a significant gap.

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 concise and front-loaded with the primary purpose. It includes required/optional labels, a parameter explanation, and an example. Every sentence earns its place, and there is no redundancy.

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 trigger action with one optional parameter and no output schema, the description covers the invocation but misses context about the result (e.g., status check, async behavior). It also fails to mention related tools like 'tiktok_get_assets_status' or 'assets_refresh_all', which could be useful for follow-up. The description is adequate but not complete.

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 adds meaning to connection_id by specifying it as a 'UUID of one tiktok_auths row', which is not present in the schema. It also clarifies that omitting it refreshes all connections. Though the schema has no description, the tool description provides useful semantic context, justifying a score above baseline.

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 action: 'Trigger the authenticated tenant's existing TikTok asset refresh flow', with a specific verb 'trigger' and resource 'TikTok asset refresh flow'. It also specifies scope (all connections or one connection_id), making it distinct from generic refresh tools. Even without naming a sibling, the purpose is unambiguous.

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 explains how to use it: either omit connection_id to refresh all active pullable connections, or provide a connection_id for one. However, it does not differentiate from the sibling 'assets_refresh_all' or mention when not to use this tool. The usage context is implied but no exclusions or alternative routing is provided.

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