Get reviews for a profile

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds useful semantic context about what the reviews contain and why they matter, but it does not disclose behavior such as pagination defaults, the difference between summary and raw formats, or how many reviews are returned.

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 two sentences with no filler. It front-loads the core return content and closes with a practically useful decision cue, making it easy for an agent to parse and act on.

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 read-only tool with no output schema, the description should explain more about the response and the page/format options. It adequately conveys the value and main content of reviews, but leaves format semantics and pagination unspecified, which is a meaningful gap for an agent deciding how to invoke it correctly.

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 only 50%, and the description does not compensate for the undocumented `page` and `format` parameters. It explains the meaning of reviews and grades but adds no semantic clarification for the format enum or pagination behavior, so an agent must infer their meaning from names and defaults alone.

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 title states exactly what the tool does — "Get reviews for a profile" — and the description adds the relevant content: per-axis grades for communication, brief definition, payment, and scope stability. It does not explicitly contrast itself with sibling tools, but no sibling appears to cover reviews, so confusion risk is low.

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 gives a clear use context: employers should check these grades before bidding, calling them the strongest available signal of project trajectory. It does not mention explicit alternatives or when not to use the tool, but that is acceptable because no obvious sibling alternative exists.

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