List boards

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

Annotations already declare readOnlyHint/openWorldHint, so the safety profile is covered. Beyond that, the description adds real behavioral context: sort order (newest first), the exact OAuth scopes required, and the fact that a bookmark cursor is returned when more pages exist — useful details the annotations cannot express.

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?

Three short sentences, front-loaded with the operation and scope, then pagination. Every clause earns its place with 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?

For a read-only list tool with no output schema, the description covers scope, ordering, scopes, and pagination behavior adequately. It could be slightly more complete by clarifying the relationship to sibling list/search tools, but nothing essential for correct invocation 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 description coverage is 100%, so all four parameters (privacy, bookmark, page_size, ad_account_id) are already well documented in the schema. The description's note that boards:read_secret is needed for secret boards duplicates the schema's own privacy note, adding no new parameter semantics. Baseline 3.

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 authenticated user's boards') plus a meaningful ordering guarantee ('newest first'). It clearly scopes to the authenticated user, which implicitly separates it from general searches, but it never names the closest sibling (pinterest_search_my_boards) to make the distinction explicit.

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 states required scopes, which functions as an implicit precondition for use, but it gives no when-to-use/when-not guidance and does not route the agent to alternatives like pinterest_search_my_boards or pinterest_get_board. Usage context is only implied.

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