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

No annotations are present, so the description carries the burden. It discloses that this is a read of cached state scoped to the authenticated tenant/connection_id, but does not describe freshness semantics, return shape, failure modes, or whether it ever invokes TikTok APIs.

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 purpose is front-loaded and the optional/required/example lines are compact and useful. No filler or repetition of the schema.

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 one-optional-parameter read tool this is largely complete: purpose, param semantics, tenant context, and example. It only lacks an explicit statement of what the returned status payload contains, which could matter since there is no output schema.

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 0%, yet the description fully compensates: connection_id is optional, is a string UUID identifying one tiktok_auths row, and scopes the cached status. The example confirms the no-argument call.

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 precise verb+resource: 'Read cached TikTok authorization asset status for the authenticated tenant.' The explicit 'cached' and 'status' wording distinguishes it from tiktok_refresh_assets and the assets_list_* 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?

Gives practical invocation details ('REQUIRED: none', optional connection_id) and implies a cached read path, but never states when to choose this over tiktok_refresh_assets or when fresh data is needed. No explicit when/when-not guidance.

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