github_actions_get_reviews_for_run

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

No annotations are provided, so the description must convey behavioral traits. It only states 'Get', implying a read operation, but does not disclose whether authentication is needed, rate limits, or other side effects. The description adds no behavioral context beyond the implied read action.

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 with no wasted words. It fronts the action. However, it is perhaps too brief and could be expanded without losing conciseness.

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?

There is no output schema, so the description should provide some indication of the return structure or typical usage context. It does not describe what 'review history' includes or how the response is formatted. Given the tool's complexity and lack of annotations, more detail is needed.

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 input schema has 100% description coverage, meaning each parameter (owner, repo, run_id) has a basic label. The description does not add any additional semantic meaning, such as format or constraints. Baseline 3 is appropriate since schema already documents parameters.

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 'Get the review history for a workflow run' clearly states the verb (get) and the resource (review history for a workflow run). It distinguishes this tool from siblings like get_workflow_run or get_pending_deployments_for_run by specifying 'review history'.

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 on when to use this tool versus other similar tools (e.g., get_pending_deployments_for_run). No mention of prerequisites, when-not-to-use, or context. With hundreds of sibling tools, this omission is significant.

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