get_board

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

No annotations are provided, so the description must carry the burden. It indicates the tool retrieves board data (likely read-only) but does not explicitly confirm idempotency, rate limits, or any side effects. The description is adequate but not rich in behavioral detail beyond the operation type.

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 concise with two sentences plus a parameter description. It is front-loaded with the main action. However, the parameter description could be integrated for even tighter structure. Overall, it is efficient with no wasted words.

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 no output schema, the description explains the return values (board, cells, custom fields, statistics). It provides enough context for a simple one-parameter tool. Could elaborate on the format or exact fields, but completeness is good for the tool's complexity.

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 has 0% description coverage, so the description compensates by explaining the 'project_slug' parameter: 'Board slug to fetch. Defaults to the configured project.' This adds meaning beyond the schema's type and default, helping the agent understand usage.

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 verb 'Get' and the resource 'board (project)' along with what is returned (cells, custom field definitions, and key statistics). This distinguishes it from siblings like list_boards (which lists boards) and get_board_cells (which only fetches cells).

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 mentions the purpose but provides no explicit guidance on when to use this tool versus alternatives. It does not state when not to use it or point to siblings like list_boards for listing or get_board_cells for just cells. Usage is implied but not clarified.

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