mdl_titles_get_reviews_page

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds nothing beyond that – no note on pagination semantics, sort ordering, or rate limits, which would be the value-add here.

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 short, but this is under-specification rather than conciseness – the single sentence conveys no information beyond the tool name and earns no place as a 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?

For a 4-parameter paginated retrieval tool with no output schema and 0% schema description coverage, the description is completely inadequate. An agent has no basis for choosing it over mdl_titles_get_reviews or for supplying correct parameter values.

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 0% across 4 parameters (page, sort, limit, title_id), so the description carries the full burden and provides none of it. It does not explain default sort ('helpful'), the page/limit interaction, or accepted title_id formats (integer vs. slug pattern).

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 'Titles: get reviews page' essentially restates the tool name (mdl_titles_get_reviews_page) rather than explaining what it does. It does not distinguish this tool from the sibling mdl_titles_get_reviews, leaving the agent to guess which one to call.

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 guidance on when to use this tool versus mdl_titles_get_reviews or mdl_reviews_get, nor any mention of prerequisites such as needing a valid title_id. Usage is only weakly implied by the name.

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