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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description usefully discloses what the profile contains and that multiple path shapes resolve to the same record, but says nothing about upstream failures, missing critics, or pagination of the embedded recent-reviews list.

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?

Two front-loaded sentences with no filler; the payload is described first and the identifier guidance second. There is minor duplication between the description's path-form sentence and the 'path' parameter description.

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?

Return contents are described and an output schema exists, both inputs are documented, and the identifier variants are spelled out, so an agent has what it needs to call it. The one residual gap is that the description doesn't indicate whether one of url/path is preferred when both are optional.

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 coverage is 100% and both parameters already document the accepted path forms, so the description largely restates existing field descriptions. Its only added value is the concrete example path, which is a marginal increment.

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 opens with a specific verb and resource ('Returns one Rotten Tomatoes critic's profile') and enumerates the payload (name, bio, flags, counts, groups, publications, recent reviews), which clearly separates it from rottentomatoes_critic_reviews and rottentomatoes_critic_publications. It never explicitly names those siblings as alternatives, so differentiation is implied rather than stated.

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 tells the agent which identifier form to supply ('/critic/mark-kermode') and points out that the '/critics/{slug}' form returned by rottentomatoes_critics_authors is also valid, which orients the agent toward the discovery tool. It stops short of stating when not to use this tool (e.g., use critic_reviews for a full review list).

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