zernio_get_pinterest_boards

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

No annotations are provided, so the description carries full burden. It discloses that the tool retrieves boards for a connected account, but does not address side effects, permissions, error cases (e.g., unconnected account), or return format.

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 a dash providing extra context. It is extremely concise with no wasted words, front-loading key 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?

Without output schema or annotations, the description fails to explain what the tool returns (list of boards) or differentiate from sibling 'zernio_list_pinterest_boards_for_connect'. This is incomplete for effective use.

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 coverage is 100% with a clear description for accountId. The tool description adds context ('connected Pinterest account') but does not provide additional meaning beyond the schema. Baseline 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 action (get), resource (Pinterest boards), and scope (for a connected Pinterest account), with a usage hint for pinning posts. However, it does not distinguish from the sibling tool 'zernio_list_pinterest_boards_for_connect'.

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 when to use (when needing to pin posts to specific boards), but lacks explicit guidance on when not to use or alternatives like 'zernio_select_pinterest_board' or 'zernio_list_pinterest_boards_for_connect'.

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