jcourse_get_review

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered structurally. The description adds value by naming what the caller receives — vote statistics and moderator notes are non-obvious side content — but does not say what happens for a missing or deleted review id, so the addition is moderate rather than rich.

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 front-loaded sentence with the verb and scope first, then the returned contents; no filler or redundancy. It is tight enough to be efficient, though the payload enumeration is a compact list rather than a prioritized statement of what matters most.

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?

An output schema exists and annotations cover safety, so the description only needs to establish selection and payload shape, which it does. The only gap is error/edge behavior for a nonexistent review id, which is minor for a read-only single-record fetch.

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?

There is a single parameter with 100% schema description coverage ('平台对象 ID，正整数' plus minimum 1), so the schema already carries the semantics. The description's 单条 reinforces that the id targets one review, but it adds no format, range, or lookup guidance beyond the schema — baseline 3 applies.

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 uses a specific verb (读取) with a precisely scoped resource (单条评价, i.e. a single review), and it enumerates the payload (full text, course info, vote stats, moderator notes, web link). The word 单条 distinguishes it cleanly from the list_* siblings such as jcourse_list_reviews and jcourse_list_course_reviews without needing to open any schema.

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?

Usage is only implied: fetching one review by id is self-evidently different from the list tools, but the description never states when to prefer this over jcourse_list_course_reviews or jcourse_get_course, and it gives no prerequisites or exclusions. The agent must infer the routing from the tool name and scope words.

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