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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new behavioral context beyond them: the listing is scoped to a single connected Pinterest account per workspace and is a prerequisite step in the Pinterest posting flow. It still omits pagination/result-count behavior.

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?

Two short sentences, both earning their place: the first defines the resource and scope, the second front-loads the actionable prerequisite. No filler.

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?

With no output schema, the description carries the burden of explaining what comes back, and it does not — an agent cannot tell whether board identifiers (needed for create_post) are returned. The workflow context is adequate but the return-shape gap leaves it only minimally complete.

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 single 'workspace' parameter has 100% schema description coverage, so the baseline is 3. The phrase 'of the workspace's connected Pinterest account' implies the workspace scoping, but the description does not clarify the optional/default-workspace semantics that the schema already gestures at, so it adds little.

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 gives a specific verb and resource ('List the Pinterest boards') and narrows scope to the workspace's connected Pinterest account, which distinguishes it from generic siblings like list_accounts or list_workspaces. It stops short of explicitly naming a sibling it differs from, which is what a 5 would require.

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?

'Required before creating a post targeting Pinterest' gives a clear workflow precondition tied to a real sibling action (create_post). It states when to use the tool but offers no exclusions or alternates (e.g. what to do if no Pinterest account is connected), so it falls short of full when/when-not guidance.

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