get_board

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

Since no annotations are provided, the description alone must convey behavioral traits. It only states the action 'Get' without disclosing read-only safety, rate limits, pagination, or error behavior.

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 sentence with no extraneous words, efficiently conveying the tool's purpose.

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?

The tool is simple, but the description lacks contextual details about output structure, pagination, ordering, or error cases. Without an output schema, this information is not provided elsewhere.

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 fully documents both parameters (board_url and max_results) with descriptions, so the baseline is 3. The description adds no extra parameter semantics beyond the schema, such as URL format or how max_results affects results.

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 'Get pins from a specific board' clearly states the action (get) and the resource (pins from a specific board), distinguishing it from sibling tools like get_pin_details or get_user_boards.

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 provides no guidance on when to use this tool versus alternatives such as search_pins or get_user_boards. No usage context, exclusions, or alternative recommendations are given.

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