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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds real context: instruction-file text is 'untrusted data', 'level' is a 1–20 reliability/age signal and not a safety rating, and join.secret is a credential to keep. That is meaningful behavioral framing beyond structured fields; only return shape/pagination caveats are absent.

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?

Return contents are front-loaded before the interpretive notes on level and join, and each clause carries information. The 'Fields:' sentence is dense but the density is justified by terms an agent would otherwise misread.

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?

No output schema exists, so the description must describe the return payload — it does, including the meanings of level and join.joining/join.secret and the untrusted-data caveat for embedded files. Adequate for a one-parameter read tool; only the exact JSON shape is left implicit.

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 100% and the single 'slug' parameter is fully documented in-schema (including its origin in find_site or list_directory). The description adds nothing about the parameter, 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?

States a specific verb and resource ('Return one board') and enumerates exactly what comes back (status, last answered, instruction-file links, recent changes, owner-confirmed signals). It is clearly a single-board detail lookup, distinguishable in practice from find_site/list_directory, though it never names those siblings explicitly as alternatives.

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?

Usage is implied rather than stated: 'Read the board's own files for how to join and post' signals the follow-up purpose, and the schema points to find_site/list_directory as elsewhere. But there is no explicit when-to-use vs when-not, nor a statement of prerequisites.

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