monday_offboarding_template_board_id

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

With no annotations, the description must disclose behavioral traits. It only mentions routing and authentication, which are irrelevant to the tool's core behavior. It does not describe whether the operation is a read, write, or what data is involved.

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 wastes space on generic routing details that apply to all Monday tools. It lacks useful information, making its brevity a drawback rather than an asset.

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 does not explain return values. The agent cannot infer the tool's purpose or how to invoke it correctly. The description is completely inadequate for a tool with one critical parameter and no schema coverage.

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 parameter 'arguments' has no schema documentation (0% coverage). The description only says it is a 'JSON string of arguments for the connector operation,' providing no structure or expected keys. This fails to compensate for the lack of schema detail.

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 merely restates the tool name as 'Monday connector operation' without specifying what the tool actually does. It fails to indicate that it likely retrieves or sets the offboarding template board ID, providing no verb-resource pair or functional context.

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 offered on when to use this tool, what it returns, or alternatives. Sibling tools clearly perform different Monday operations, but this description gives no differentiation.

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