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

The annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds useful context about returned content, namely notes, pictures, and contributor attribution, but it does not mention pagination, permissions, empty-board behavior, or how lookup behaves when both optional parameters are omitted.

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 a single efficient sentence with no redundant wording and the key returned artifacts are front-loaded. It is structurally concise, though it reads more like a label than a fully actionable instruction.

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?

For a simple read-only tool with two optional, fully described parameters and an annotation-covered safety profile, the description gives a minimal picture of the returned content. It remains incomplete about parameter interaction and return format, which matters because there is no output schema.

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%, so both projectId and projectName are already documented structurally. The description adds no further meaning about parameter precedence, partial name matching, or whether either parameter is sufficient on its own, so the baseline of 3 is appropriate.

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 clearly identifies the resource: notes and pictures on a project's shared board, including who added them. It implies retrieval through the tool name rather than an explicit verb, and it does not explicitly distinguish itself from nearby tools such as addBoardNotes.

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 when-to-use guidance, no mention of alternatives, and no explanation of when to use projectId versus projectName. The description merely states what the board contains, leaving callers to infer invocation context from the tool name and schema alone.

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