mdl_titles_get_reviews

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds nothing beyond that: no pagination behavior, no result-count or ordering notes, nothing about what a title_id with no reviews returns. The bare name-restatement leaves the burden on the annotations.

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 and front-loaded, which is fine, but it is a four-word restatement of the name that conveys no information, so the brevity is under-specification rather than economy.

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 no output schema, one undocumented parameter, and a crowded set of sibling review tools, the description should explain return shape or pagination and how it differs from mdl_titles_get_reviews_page. None of that is present.

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%, so the description must compensate, but it says nothing about title_id — not whether it accepts either the integer or the alphanumeric string form defined in the anyOf, nor any lookup behavior. The one required parameter is completely unexplained.

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 restates the tool name nearly verbatim ('Titles: get reviews'), giving a verb and resource but no scope. Siblings like mdl_titles_get_reviews_page indicate this likely returns a first/unpaginated set, yet the description does not distinguish it from that sibling or from mdl_reviews_get.

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?

No when-to-use guidance, no prerequisites, and no mention of the obvious alternative mdl_titles_get_reviews_page or mdl_reviews_get. The agent gets no signal for choosing among the several review-retrieval siblings.

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