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

Adds real context beyond the readOnlyHint/openWorldHint annotations: that results are truncated without auth, that a Bearer tt_ token bills TidyTools credits, that x402/Apify payment works without an account, and exact free-tier quotas (3/IP/day, 50 per ASN pool, 100 global). This is precisely the kind of cost and limit disclosure annotations cannot carry. It stops short of describing what a 'limited free result' actually contains or how 'recent' is defined.

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 purpose, then cost/auth, then limits — a sensible order. The billing and x402 sentences are dense and slightly repetitive about paid access, but every sentence carries actionable information for the caller.

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 read-only, single-parameter tool with no output schema, the definition covers purpose, auth, pricing, and quotas well. The one real gap is what the returned review looks like and how much is withheld in the free tier — relevant since there is no output schema to lean on.

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?

One parameter at 100% schema coverage ('One app ID or store URL'), so the schema already does the work. The description reinforces singularity ('for one app') but adds no format, examples, or accepted URL shapes beyond the schema text.

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?

Opens with a specific verb and resource: 'Reads one recent Apple App Store review.' The 'one app' scoping distinguishes it in spirit from app_store_details/play_store_details, but no sibling is named explicitly, so an agent must infer the boundary.

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 explicit exclusions ('Not for batch work or unrestricted monitoring') and a scope constraint ('Use for one app'), which is well above average. It never names the obvious alternative (app_store_details) for agents who actually want metadata rather than a review, leaving that routing to inference.

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