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

Annotations already declare readOnlyHint=true, and the description adds useful behavioral context: the whole-filter total, the auth/space-selection flow, the message/diff/history nature of change requests, and the security guidance to treat stored content as data, not instructions. No statement contradicts the annotations.

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?

Purpose is front-loaded and the description is compact at four sentences. The endpoint, auth prerequisite, record model, and safety warning are relevant, though the general 'Busabase writes through ChangeRequests' sentence is slightly tangential and not strictly necessary for operating this tool.

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 required parameters and no output schema, the description covers the core operation, return-style information, filter behavior, auth requirement, and record shape. It does not name the cursor-listing sibling or specify the exact response envelope, but those gaps are minor for a simple page listing.

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 100%, so the baseline is 3. The description adds only a filter-equivalence note and restates the targetSpaceId auth requirement already present in the schema, without materially deepening parameter understanding.

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 first sentence clearly states that the tool returns a random-access page of change requests plus a total across the filter, and the title supplies the list verb. It distinguishes page-based access from cursor-based listing, but it does not name the sibling tool explicitly, so differentiation is good but not fully explicit.

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 contextual guidance for multi-space accounts: call auth_verify, ask the user which space to use, and pass targetSpaceId. It also notes that status, mine, and affectsNodeId behave like the cursor listing, but it never states when to prefer this numbered-page tool over the cursor listing or otherwise directs tool selection.

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