monday_get_item

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

With no annotations, the description must disclose behavior. It mentions routing and scope but not whether the operation is read-only, error handling (e.g., if item not found), authorization requirements, or any side effects.

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 and front-loaded with the name, but it wastes space on routing details that are irrelevant for selecting or invoking the tool. Could be more concise by removing boilerplate and adding useful information.

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?

Even though an output schema exists, the description does not mention return values or how to interpret results. It lacks critical context such as the need for an item identifier, making it incomplete for effective use.

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 sole parameter 'arguments' is described as a 'JSON string of arguments for the connector operation,' which adds no meaning beyond the schema. It fails to specify required fields (e.g., item ID) or format, leaving the agent without guidance on how to construct the JSON.

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 repeats the tool name ('get_item') and labels it as a 'connector operation' without explaining what an 'item' is in Monday.com context. It fails to specify that this tool retrieves a specific item from a board, leaving the purpose vague.

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 is provided on when to use this tool versus siblings like monday_list_items, monday_search_items, or monday_get_board. The description offers no context for selection.

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