tiktok_get_search_ads_maturity

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

Without annotations, the description carries the behavioral burden. It does state 'Read-only diagnostics only,' which is useful and prevents assumptions of mutation. But it does not explain how maturity is derived, whether multiple endpoints are called, or any rate-limit/auth implications, so transparency is only partial.

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 short sentences, front-loaded with the core purpose. The 'read-only diagnostics only' phrase adds safety context without wasting space. Every clause earns its place.

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?

The description lacks operational context: no return format, no explanation of what 'maturity' means or how to interpret the result, and no mention of the required advertiserId or date defaults. With no output schema and six parameters, this is a significant gap for an un-annotated 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?

Schema description coverage is 67%, so most parameters are already documented. The description adds some meaning by connecting seedKeywords to 'optional keyword recommendation endpoints' and implying date parameters bound reporting. It does not substantially clarify limit or dataLevel beyond what the schema/enum provides.

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 states a specific verb ('Diagnose') and resource ('TikTok Search Ads maturity'), and identifies the data sources. It is clearly distinct from the many generic tiktok_get_* sibling tools. The term 'maturity' is somewhat vague, and no sibling comparison is made, so it falls short of a perfect 5.

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 implied: use this when you need to diagnose TikTok Search Ads maturity. However, the description does not explicitly say when NOT to use it, nor does it name alternatives or exclusions, leaving routing decisions to inference.

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