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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so the bar is lower, yet the description still adds real context: data is 'read live from Pinterest,' failure occurs when Pinterest is not connected or the list cannot load, and currentBoardId is null if unset. It does not cover pagination or freshness/latency behavior, so not a 5.

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?

Four compact sentences, front-loaded with what is returned and followed by usage, failure modes, and related tools. 'Does not change anything' is mildly redundant with readOnlyHint/destructiveHint annotations, a small amount of non-earning text.

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?

An output schema exists so return values needn't be spelled out, yet the description still names fields and the null case; combined with failure conditions and the related-tool routing, an agent has everything needed to call this zero-arg, read-only tool correctly.

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?

Zero input parameters, so the baseline is 4. The description's explanation of currentBoardId describes output semantics rather than inputs, which adds value but is technically beyond the parameter dimension.

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 ('Lists the connected Pinterest account's boards') with the returned fields enumerated, and explicitly disambiguates from siblings set_pinterest_board and list_channels. An agent can tell this apart from other list_* tools immediately.

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?

Gives a concrete use case: 'turn a board the requester names into its id, for a post's boardId or for set_pinterest_board,' plus the failure condition when Pinterest is not connected. It doesn't explicitly state when NOT to use it or compare against list_channels beyond the trailing 'Related' line, so it stops short of 5.

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