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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered; the description still adds that data is read live from Pinterest's API with that account's token and that the response is limited to that single account. It stops short of describing limits, pagination or empty-board behavior, so it is a solid addition rather than a complete one.

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?

Front-loaded with the scope and the read-only guarantee, then the chaining advice, then the rejection rule. Dense and mostly waste-free, though the mid-sentence create_post/update_post detour pushes it slightly past what a list tool needs.

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?

One required string parameter documented in both schema and prose, an output schema covering return shape, and annotations covering safety. Nothing an agent needs to call this correctly is missing.

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%, so baseline is 3, but the description adds two things the schema does not: accountId must be a Pinterest account (other platforms are rejected) and the resulting board name/id is what feeds the `board` argument elsewhere. That cross-tool linkage is genuine semantic value.

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+resource ('List the boards') scoped to one connected Pinterest account, and the very first clause disambiguates it from list_accounts and from the media/post tools. An agent knows exactly what it gets back without reading the schema.

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?

Explicitly gives the downstream use case ('a post targeting Pinterest must name one — pass the board name or id as `board` on create_post/update_post'), the prerequisite for the argument ('accountId is a Pinterest account id from list_accounts'), and the exclusion ('other platforms have no boards and are rejected'). That is when-to-use, how-to-chain and when-not in three sentences.

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