invariance_review_get

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

The readOnlyHint and openWorldHint annotations already disclose the central behavioral property (non-mutating). The description adds no further behavioral context, such as error scenarios (not found), ownership/auth requirements, or the shape of the returned review. Despite the lower burden due to annotations, the description offers no incremental behavioral disclosure and relies entirely on the structured hints.

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 one clean sentence that states the action and the parameter, has zero filler, and front-loads the verb and resource. It is appropriately terse for an operation that takes a single ID and returns a review 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?

For a simple GET-by-ID operation, the description tells an agent exactly what to call if it already knows the ID. However, no output schema exists and the description does not explain the return contract (the review's structure) or behavior when the ID is invalid/not found. Given the low complexity, this is not fatal, but the contract remains incomplete for an agent that needs to consume the result reliably.

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 only defines an 'id' string with no description (0% coverage). The phrase 'by ID' clarifies that the id is the review identifier, which adds slight semantic value beyond the bare schema, but it does not describe the ID's format, constraints, or uniqueness requirements. For a single self-explanatory parameter, this is minimally sufficient.

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 states the exact verb (Get), resource (review), and the lookup key (ID). This is a specific and unambiguous purpose, and it clearly distinguishes the tool from sibling tools like invariance_review_list or invariance_review_resolve without requiring opening 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?

The description implies that the tool should be used when you have a known review ID and need that single object, but it never explicitly says that, nor does it mention alternatives like invariance_review_list for browsing reviews. The guidance is left to inference, with no when/not-to-use instructions.

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