list_grids

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

With no annotations, description carries full burden. It discloses limit cap (OPENPROJECT_MAX_PAGE_SIZE), default 50, pagination via next_offset, and optional scope filter. Missing edge cases like empty results or error handling, but still strong.

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: first states purpose, second provides pagination details. Front-loaded, no redundant information, optimally concise.

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?

Without output schema, description should hint at return structure but doesn't. Adequate for basic listing with pagination, but incomplete for a 3-parameter tool with no annotations.

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 description must compensate. It clarifies scope as a page path and explains limit cap and pagination. However, offset parameter explanation is confusing (refers to next_offset not in schema) and no details on return format.

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?

Description clearly states 'List dashboard grids, optionally filtered by scope (page path).' It specifies the action (list), resource (dashboard grids), and optional filtering, distinguishing it from sibling tools like get_grid.

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?

Provides pagination guidance (limit cap, next_offset usage) but does not explicitly state when to use this tool vs. alternatives like get_grid or list_views. Context is clear but lacks exclusionary guidance.

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