get_pinterest_board

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It fails to mention that this is a read-only operation, whether authentication is required (though access_token param hints at it), what happens if the board_id is invalid, or any rate limits. The description is completely silent on these aspects.

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, concise sentence that directly states the tool's purpose. There is no unnecessary information, and it is well-structured for quick comprehension.

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 GET tool with two parameters, the description is minimal but adequate. It lacks information about what 'details' entails, no output schema, and no error handling context. However, given the tool's simplicity and the presence of sibling tools, a score of 3 is reasonable.

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 schema covers 50% of parameters (board_id has a description, access_token does not). The description adds no extra meaning beyond the schema. However, the parameter names (board_id, access_token) are relatively self-explanatory, so the baseline score 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 states the tool's purpose: retrieving details of a specific Pinterest board. The verb 'Get' and resource 'details of a specific Pinterest board' are specific and distinguish it from sibling tools like list_pinterest_boards (which lists multiple boards) or create_pinterest_pin (which creates a pin).

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?

No guidance is provided on when to use this tool vs alternatives (e.g., list_pinterest_boards). It does not mention prerequisites such as needing a board_id obtained from another tool. The description lacks any context about appropriate use cases.

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