query_items

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

Annotations already provide readOnlyHint=true, and the description adds valuable hidden behavior: the API defaults to 50 items per page, and the tool pages through and concatenates results unless limit/page are given. This is a meaningful behavioral disclosure beyond the annotation.

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?

Two sentences, with the purpose front-loaded and the pagination caveat expressed compactly. Every sentence adds value and there is no redundancy.

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 tool, the description covers the main behavior, default output size, and pagination behavior. It lacks an explicit return shape and explicit sibling routing, but the readOnlyHint and simple list semantics make it fairly complete.

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 description adds semantic context for limit/page by explaining the default page size and concatenation behavior. However, it does not explain projectId or boardId, and schema coverage is only 50%, so the required parameters are only partially compensated for.

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 action ('List') on a specific resource ('items (rows) of a board') and clarifies the return content ('including their cell values'). This clearly distinguishes it from sibling tools like list_boards or list_comments.

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 use for retrieving board items and explains pagination behavior, but it does not explicitly mention alternatives or say when not to use this tool. Among many list/query siblings, the agent is left to infer selection criteria.

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