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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and network scope are covered without the description. The word 'live' adds a small amount of behavioral context about freshness, but nothing is said about coverage, pagination, or what the inventory contains. With annotations carrying the safety profile, a 3 is appropriate.

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?

It is a single front-loaded sentence with no filler, which is structurally sound. However, the brevity comes from under-specification rather than efficiency — the sentence communicates almost nothing an agent can act on beyond the resource name.

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?

With 0 parameters, an existing output schema, and annotations covering read-only/open-world, most of the structured burden is already handled elsewhere. What remains missing is the one thing only the description can supply: what this returns and how it differs from rottentomatoes_sitemap_urls.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No parameter-level detail is expected or missing here.

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?

Names the resource ('Rotten Tomatoes ... sitemap inventory') and the freshness attribute ('live'), but the verb is left implicit — it never says whether it lists sitemaps, fetches one, or enumerates pages. It also gives no differentiation from the sibling rottentomatoes_sitemap_urls, which an agent would need to choose between.

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?

There is no when-to-use guidance at all: no statement of what question this answers, no condition for choosing it over rottentomatoes_sitemap_urls, and no prerequisites. The agent must infer usage purely from the name.

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