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

With no annotations, the description carries the full burden of behavioral disclosure. It does state that the operation is a read ('Read') and clarifies the semantic boundary between this view and what_changed_since. However, it does not explain pagination behavior, default filtering, or whether results are limited to certain repositories, which are meaningful gaps for an unannotated tool.

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 concise sentences with no filler. It front-loads the core purpose and then adds a single clarifying contrast with what_changed_since. Every word earns its place.

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?

The description provides enough to understand the tool's purpose and main distinction from a sibling, but it omits parameter behavior and expected return shape, and there is no output schema to compensate. For a list tool with three optional parameters and no annotations, the definition is adequate but not complete enough for confident invocation without further inference.

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 0%, so the description needed to compensate for the parameters, but it mentions none of them. Offset, review, and repositoryId are left entirely to the schema, whose enum values help somewhat but do not explain semantics like what 'attention' means or how repositoryId interacts with the shared-repository scope. The description adds no parameter-level meaning.

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 uses a specific verb ('Read') with a clear resource ('impact and repair status') and scopes it to 'repositories explicitly shared with this agent.' It also distinguishes itself from what_changed_since, making the tool's role immediately clear. The distinction from 'inspect_repair' is implicitly handled by the word 'list.'

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 clear context for when to use this tool: to view proposed fixes and checks rather than original external changes. It explicitly contrasts with what_changed_since, which is the main conceptual alternative. However, it does not mention inspect_repair or list_maintained_repositories as alternatives, so the guidance is not exhaustive.

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