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

Annotations already declare readOnlyHint/idempotentHint/openWorldHint and destructiveHint=false, so the safety profile is covered. The description goes well beyond that: it discloses that output can carry a chart_provenance token valid for 15 minutes on any replica, that chart_render labels unverified values as unverified_model_data, and that an attribution footer must be reproduced verbatim — genuinely useful output behavior, especially with no output schema.

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 opening purpose sentence is front-loaded and efficient, but the description then runs long with provenance/attribution rules and a 'data accuracy contract' referencing campaign budgets, ROAS, CPA, and revenue — advertising metrics that are irrelevant to a project-management connector and read as boilerplate copied from another tool. That bloat dilutes an otherwise well-structured definition.

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?

With no output schema and a nested params object, the description compensates by describing output artifacts (provenance token, attribution footer) and verification semantics. The per-action return shapes are left to the enum descriptions, but nothing critical for correct invocation appears to be missing.

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 100% and the action enum plus params object already enumerate every action and its arguments. The description only adds conceptual aliasing (items = rows = pulses) and resource vocabulary, not syntax or constraint detail beyond the schema, so the baseline 3 applies.

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 names the resource domain precisely (Monday.com workspaces, boards, groups, columns, items/rows/pulses, owners, statuses) and states its purpose ('Use for Monday.com board data and project/task status questions'). It distinguishes itself from the many other *_connector siblings by being Monday-specific, though it does not explicitly name a competing tool it is not.

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?

It gives a clear usage context ('Use for Monday.com board data and project/task status questions') and adds downstream routing guidance to chart_render when a visual/trend/recap is requested. It stops short of explicit when-not-to-use or naming alternative connectors for overlapping data.

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