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

Beyond the readOnlyHint and openWorldHint annotations, the description reveals important behavioral traits: the image excludes diagram cards, groups, and cross-links; it returns a PNG plus a one-line summary; format='svg' returns the vector source as text; and scale is clamped to keep the image inline-able. This prevents false negative conclusions about writes.

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 dense but efficient: it front-loads the main action and purpose, then adds the critical caveat about what is not drawn, and ends with the alternative tool. Every sentence contributes either to selection, invocation, or interpretation of the result.

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 lack of an output schema, the description sufficiently explains the return value ('PNG plus a one-line summary') and the SVG variant. It also covers behavioral caveats and the sibling alternative, so an agent has enough context to select and invoke the tool correctly without additional ambiguity.

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 input schema already documents all 7 parameters with defaults and descriptions, so the baseline is 3. The description adds meaningful context beyond the schema, such as the scale clamping behavior, that SVG format returns the source as text, and that the result is a PNG plus summary. This enriches parameter understanding without being redundant.

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 uses a specific verb and resource: 'Render a project's board as an image and return it.' It clearly states what the image contains—tables, enums, relationships, sticky notes, drawings, pasted images—and differentiates itself from the structural board tool by warning that diagram cards, groups, and cross-links are not drawn.

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 explicit use cases: 'Use this to SEE the board - to check a layout you just wrote, or to find cards that overlap or sit far from what they relate to.' It also gives a when-not-to-use signal by stating that an absent frame or connector is not evidence the write failed, and routes the agent to get_board for those elements.

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