monday_list_boards

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

Describes routing through an API path with JWT/tenant scope, implying authentication. However, no annotations are provided, and the description does not explicitly state if it is read-only or disclose any side effects. The read-only nature is implied but not confirmed.

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?

Three sentences are concise but lack structure. The description mixes operation identification, routing info, and parameter description without clear separation. It is not overly verbose but could be better organized.

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?

Given the tool has one parameter and an output schema exists, the description fails to explain what the output contains or how to structure the arguments. It is incomplete for an agent without prior knowledge of the Monday API.

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 single 'arguments' parameter is described as a 'JSON string of arguments for the connector operation.' This adds minimal meaning beyond the schema; it does not specify valid keys, structure, or defaults. With 0% schema coverage, more detail is needed.

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?

Clearly states the tool lists boards ('list_boards') with a verb and resource. However, it doesn't specify scope (all boards? user-specific?) or differentiate from siblings like monday_get_board.

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?

No guidance on when to use this tool versus alternative tools (e.g., monday_get_board for a single board, monday_search_items for searching). Does not mention prerequisites or exclusions.

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