monday_list_items

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

Annotations are absent, so the description bears full burden. It fails to disclose any behavioral traits: whether it is read-only, what it returns (output schema exists but is not mentioned), or any side effects. Agent cannot infer safety or expected outcome.

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 short but includes irrelevant routing details ('Routes through /api/tools/invoke...') and tautology ('Monday connector operation list_items'). It is not structured to front-load the core purpose, wasting space on context that doesn't help selection.

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?

Despite having an output schema, the description lacks essential context about what items are being listed and what the output contains. Among many Monday list tools, this description is insufficient for an agent to correctly invoke it without additional information.

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 coverage is 0%, requiring description to compensate. The description says the 'arguments' parameter is a 'JSON string of arguments for the connector operation' but does not specify which keys (e.g., board_id, group_id) are expected. This adds minimal value beyond the schema itself.

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 it is a 'Monday connector operation list_items' but does not specify what items (e.g., board items, workspace items) or distinguish it from sibling tools like monday_list_boards or monday_list_subitems. The purpose is vague and leaves ambiguity.

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 alternatives. There is no mention of prerequisites, context, or when not to use it. The description only provides routing and argument format, which does not help an agent decide to invoke this tool.

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