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

Adds meaningful context beyond the annotations: 'Costs no credits' is billing behavior not covered by readOnlyHint, and the SIGN-IN REQUIRED block discloses the OAuth vs API-key auth paths with a concrete header format and where to create the key. Annotations already cover safety, so this extra operational detail is valuable. Minor gap: no pagination behavior for large accounts.

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 core action, then the return fields, then the cost note, then the auth requirement. Every clause earns its place and nothing is redundant.

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 an output schema present, the description need not explain return values further, and it covers cost, auth, and usage routing. For a zero-param read tool this is 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?

Zero parameters, so the baseline is 4. The description correctly documents the shape of the response items even though there is no input to describe.

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 (List) and resource (boards/visual canvases) and enumerates the returned fields (id, name, revision, card count, page link), so the agent knows exactly what comes back. Sibling tools like list_generations, list_saved_ads, and list_ugc_avatars are clearly differentiated by resource.

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 says 'Start here to pick a board or to see that none exists yet', naming both when to use it and the selection decision it enables. The zero-arg, zero-cost nature makes it an obvious first call, and no alternative could serve the same purpose.

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