get_pinterest_board

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered; the description only restates that this is a retrieval. It adds no context on authentication needs (the access_token parameter), rate limits, or what happens when a board ID is invalid or private.

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?

A single front-loaded sentence with zero filler. There is no redundancy or trailing caveat to trim; the issue is under-specification elsewhere, not verbosity.

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?

There is no output schema, so the description is the only place an agent could learn what a board's 'details' include (name, description, owner, pin counts) and how to handle errors or private boards. With one of two parameters undocumented and no return-shape guidance, the definition is too thin for an open-world fetch 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?

Schema description coverage is only 50%: board_id is documented solely as 'Board ID' and access_token has no description at all. The description offers no help here, leaving unclear whether board_id is a numeric ID, slug, or username-qualified path, and whether access_token is optional or required for private boards.

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 (get) and resource (Pinterest board) with the scope narrowed to a single board by 'specific', which implicitly separates it from list_pinterest_boards. It does not explicitly name a sibling or say what 'details' comprises, so an agent must infer the boundary from the name alone.

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 sentence describes when to call this versus list_pinterest_boards, list_pinterest_pins, or get_pinterest_user, and no prerequisite (e.g., needing a board ID obtained elsewhere, or authentication) is stated. The get-vs-list distinction is left entirely to the reader's inference from the tool name.

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