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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds a genuine behavioral trait beyond them — that the status is read from a cache rather than fetched live — which tells the agent results may be stale and that refresh is a separate tool. It still omits rate limits, auth prerequisites, and what the status represents.

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?

Front-loaded with the core purpose, then a compact REQUIRED/Optional block and a concrete zero-argument example call. 'REQUIRED: none' is mildly redundant with the schema, but every other line earns its place and nothing is padded.

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 parameterless-required read tool with no output schema, the description is adequate on inputs but says nothing about what 'asset status' returns or how to interpret it, which the agent must guess. It also does not mention authtoken/tenant prerequisites despite referencing 'the authenticated tenant'.

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 description coverage is 0%, so the description carries the burden, and it documents only one of the two parameters ('connection_id — UUID of one tiktok_auths row'). The second parameter, connection_context (pattern ^mctx_v1_[0-9a-f]{64}$), is left entirely unexplained, presumably because it is injected by the harness, but the agent gets no confirmation of that.

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 and resource — 'Read cached TikTok authorization asset status' — with an explicit scope ('for the authenticated tenant'). The word 'cached' separates it from the sibling tiktok_refresh_assets, but no sibling is named outright, so an agent must infer the distinction.

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?

Usage is only implied: 'cached' hints that this is the cheap, non-refreshing read and 'optionally scoped to one connection_id' hints at the filtered vs unfiltered case. There is no explicit when-to-use/when-to-prefer-tiktok_refresh_assets statement or mention of prerequisites such as an existing tiktok_auths row.

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