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

Annotations already provide readOnlyHint, openWorldHint, and idempotentHint, so the description does not need to repeat safety traits. It adds value by disclosing 'One page only' (a pagination limitation not captured in annotations) and specifying the output includes image URLs and stats. This goes beyond the annotation set without contradicting it.

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 a single, tight sentence that front-loads the core purpose and a key limitation. There is no wasted wording, and every element ('keyword search', 'photo-mode', 'image URLs and stats', 'one page only') contributes directly to agent understanding. It is exemplary in brevity and structure.

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 straightforward search tool with no output schema, the description covers the essential aspects: what it searches, what it returns, and the one-page constraint. It does not mention error handling or alternative output formats, but these are not critical for basic invocation. The description is sufficiently complete for an agent to call it correctly.

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 100%—all three parameters (q, count, expand) are documented in the schema. The description adds no parameter-specific detail beyond what the schema already provides, so it does not enhance parameter understanding. Baseline 3 is appropriate because the schema does the heavy lifting.

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 verb ('search'), the resource ('photo-mode (carousel) posts'), and the output ('image URLs and stats'). It distinguishes this tool from sibling search tools by explicitly narrowing to photo-mode content, which separates it from tiktok_search_videos, tiktok_search_sounds, etc.

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 implies usage for photo posts but does not explicitly contrast with alternative search tools or provide conditions for when not to use it. The 'One page only' note is a limitation, not a usage guideline. There is no mention of when to choose this over tiktok_search_videos or other searches, leaving the agent to infer based on the content type.

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