get_peer_review_assignments

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

Annotations include readOnlyHint: true, and the description does not contradict this. It adds minimal context by indicating the output includes a mapping with completion status, but does not explain details like whether pagination is involved, how completion is determined, or any additional side effects. Since annotations already cover safety, a score of 3 is appropriate.

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?

The description is a single sentence that efficiently conveys the core purpose without unnecessary detail. It is well-structured and front-loaded with the action and object.

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?

Given the tool's moderate complexity and the abundance of sibling peer-review tools, the description is somewhat sparse. While the schema and annotation provide structural safety, the description does not clarify what distinguishes this mapping from list_peer_reviews or analytics tools, leaving potential ambiguity. However, for a straightforward read-only operation, it may suffice.

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 100%, so the baseline is 3. The description does not add clarification beyond the schema; it mentions 'completion status' but that likely refers to output, not parameters. No parameter-specific guidance is provided.

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 clearly states the tool retrieves a peer review assignment mapping, specifying the resource (peer review assignments) and the key aspects (who reviews whom, completion status). However, it does not differentiate from sibling tools like list_peer_reviews or get_peer_review_completion_analytics, which may serve similar purposes.

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 guidance is provided on when to use this tool versus the many peer-review-related siblings. The description lacks any mention of preferred use cases, exclusions, or alternative tools, leaving the agent to guess which mapping tool is appropriate.

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