get_semantic_reviews

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

No annotations are provided, so the description carries the full burden, and it does disclose meaningful behavioral traits: the queue is append-only, tallies are advisory and surface-bound, and reviews never create proposal relations. This gives strong side-effect and safety context, though 'surface-bound' and 'advisory' remain underdefined.

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?

Two sentences with no filler: the first front-loads the resource identity and the second clarifies a key side-effect. The dense jargon costs some immediate clarity but the description is appropriately sized.

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 nullary read with no output schema, invocation is trivial and the side-effect guarantee is useful. However, the description doesn't explain what a review item contains, what 'lexical-candidate' means, or what the tallies look like, so an agent must infer the expected return structure from the name and surrounding domain context.

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?

The schema has zero parameters and 100% coverage, so there is nothing for the description to add about parameters. The basline 4 applies because no parameter documentation is needed.

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 identifies the resource as a 'deduplicated lexical-candidate review queue' with 'advisory tallies,' which conveys the subject matter and loosely distinguishes it from generic queues. However, it is a noun phrase describing the queue rather than a statement of what the tool does (e.g., returns/lists reviews), leaving the action implicit.

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 explicit when-to-use guidance or mention of alternatives among the many sibling tools. The 'review queue' phrasing implies use when semantic review data is needed, but an agent gets no exclusions or selection criteria.

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