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

The annotations already establish readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the description does not need to restate safety. It adds useful behavioral context by clarifying the result includes both written reviews and an average score, though it omits ordering, pagination, and empty-result behavior.

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?

One compact sentence states the resource and outcome without filler, and the essential content appears immediately. Nothing in the description is wasted or redundant.

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 tool with minimal parameters and annotations covering safety, the description is reasonably complete. It names the expected return content, and the schema fully explains the parameters. Minor gaps are the absence of review ordering, pagination details, and empty-case behavior, but these are not critical for correct selection.

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 have meaningful descriptions: tutorUserId accepts either a search result id or a profile handle, and limit defines range and default. The description adds no extra parameter semantics beyond saying 'for a tutor,' so baseline 3 is appropriate.

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 states a specific verb 'get', a clear resource ('recent written reviews and the average score for a tutor'), and differentiates this from sibling tools like search_tutors and get_tutor by focusing on reviews rather than tutor discovery or profile data.

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?

The description implies usage when a tutor's reviews are needed, and the parameter description references search_tutors results, but it does not explicitly say when not to use it or name an alternative. The intended context is reasonable, but the guidance is left largely to inference.

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