get_board

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

With no annotations provided, the description carries the full burden. It states the tool returns all sections, posts, and comments, but provides no details on side effects, return structure, permissions, pagination, or error behavior. This is a significant gap for a read tool with complex output.

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 two concise sentences, front-loaded with the primary purpose and followed by a key parameter clarification. Every sentence earns its place, with no redundant information.

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 tool has one parameter, no output schema, and no annotations, the description covers the essential purpose and parameter origin. However, it omits details on the return format (beyond 'organized form'), potential large result sets, or error cases, leaving gaps for an agent to fully understand invoking this tool.

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 parameter board_id has zero schema description coverage, but the tool description compensates by explaining it is a 16-digit ID from list_boards, not the URL slug. This adds critical semantic meaning beyond the schema's minimal type/required fields.

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 states the tool fetches all sections, posts, and comments of a single board and returns them in an organized form. This is a specific verb+resource that distinguishes it from the sibling list_boards, though it does not explicitly contrast the two.

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?

The description implies usage by explaining that board_id is obtained from list_boards, suggesting a sequential workflow. However, it does not explicitly state when to choose this tool over alternatives or provide exclusions, so guidance is only implied.

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