list_project_items

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds that the tool returns field values for each card and supports status-oriented backlog reads. It does not discuss pagination or response size, but pagination is explained in the schema and output schema exists.

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 that front-loads the action and resource, then adds the motivating use case. There is no filler, repetition of schema fields, or redundant annotation language.

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 list operation with an output schema and pagination parameters described in the schema, the definition provides the necessary understanding: board scope, field-value details, and status-based use. It could more explicitly describe the identifier semantics for project_owner and project_number, but those are reasonably inferable. Overall, an agent has enough context to select and call the tool correctly.

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 50%, with after and per_page well documented but required project_owner and project_number lacking schema descriptions. The description ties the operation to a 'project board', helping an agent infer that these parameters identify the board, but it does not explain owner format or how to obtain the project number. The parameter names are mostly self-explanatory, so the description adds only modest value.

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 a specific verb ('Lists') and a resource ('project board'), and clarifies that each card's field values are returned. The phrase 'backlog can be read by Status rather than one issue at a time' differentiates it from single-item tools and from board-mutation tools. This makes the tool's purpose unambiguous relative to siblings.

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 explicitly frames the tool for reading a backlog by Status in bulk, which is clear usage context. It implies the alternative of reading one issue at a time but does not name a specific sibling tool or state when not to use it. The guidance is clear but not fully explicit.

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