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

Annotations already declare a safe, idempotent, closed read, so the bar is lower. The description adds genuine behavioral value beyond them: sort order ('newest first'), the exact inclusion rule (all account briefs plus this board's draft), and the shape of each item (status, looks, automations, credits, covers).

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?

A single dense sentence that front-loads the resource and ordering before the scope enumeration. No filler, though the trailing field list makes it slightly heavy.

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 the description usefully enumerates returned fields, and the tool is a simple 2-param read, so safety and scope are covered. However, the page parameter and pagination behavior are unexplained, leaving an agent unable to call the tool correctly for multi-page results.

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 only 50%: board_id is documented in the schema but the page parameter has no description anywhere. The description never mentions pagination or what board_id scopes, so it does not compensate for the coverage gap.

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?

States a specific verb+resource (list the account's Shoot Board briefs) and even defines the exact scope returned: every brief that ran plus this board's draft. It does not name or differentiate against siblings like get_brief or mcp_brief_runs, so it stops short of a 5.

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?

There is no explicit when-to-use guidance and no alternative is named. The scope sentence ('every brief that ran ... and this board's draft') implies this is the broad listing versus get_brief's single fetch, but the agent must infer that rather than being told.

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