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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the returned field inventory, but does not disclose behavioral details such as pagination, error behavior, or authentication requirements; the output schema already carries return-value details.

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 purpose is front-loaded in the first sentence, followed immediately by the input form. Two sentences, no filler, and every clause contributes either scope or input guidance.

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 simple read-only retrieval tool with full schema coverage, annotations, and an output schema, the description is complete enough to invoke correctly. The only meaningful gap is that it does not explain when to supply url versus path, or whether one of the two is effectively required.

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 the baseline is 3. The description repeats the accepted /critic and /critics path forms and adds a concrete example, but it omits the /profiles/critic form documented in the schema and does not clarify how the optional url and path parameters relate to each other.

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 starts with a specific verb and resource: 'Returns the publications one Rotten Tomatoes critic writes for.' It also enumerates the returned fields, making clear how this differs from critic reviews or publication detail tools.

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?

It gives useful input guidance by showing a critic path example and noting that the /critics/{slug} form from rottentomatoes_critics_authors also works. However, it never says when to use this tool instead of rottentomatoes_critic, rottentomatoes_critic_reviews, or rottentomatoes_publication, and it provides no exclusions.

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