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

Goes well beyond annotations by disclosing cost model ('charged on its own', 'Uses credits (see get_account)'), an asynchronous fallback with a concrete latency window (~40 seconds) returning a job_id for get_competitor_results, and the qualitative output ('why each one fits'). These are exactly the operational traits an agent needs and that readOnlyHint/openWorldHint cannot convey.

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?

Four compact sentences, front-loaded with the core purpose, then workflow, then cost/async behavior. Every sentence carries information not duplicated in schema or annotations; 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?

There is no output schema, and the description compensates by explaining both return shapes (results inline or a job_id to poll via get_competitor_results) and the latency threshold that selects between them. For a cost-bearing, open-world search tool, nothing critical is missing.

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%, so focus, language and platform are already documented, including the enum values. The description only adds the constraint that a single call searches one platform, which is marginal but consistent with the schema baseline of 3.

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 ('Finds creators in the same niche') plus the exact platform scope (Instagram, TikTok or YouTube) and the differentiating output ('why each one fits'), which separates it from siblings like find_viral_posts and get_creator_profile.

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 clear downstream context ('Use it to choose whom to follow with track_creator') and states the per-call constraint that each call covers one platform, so the agent knows to call it repeatedly per platform. It does not state when not to use it, e.g. versus find_viral_posts, so it stops short of full routing guidance.

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