List your pinned feeds

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering safety. The description adds minimal behavior beyond that—only that results are 'in order'. It doesn't disclose pagination, limits, or other operational details, which is acceptable given annotations but adds little extra context.

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 sentences, no filler. The first sentence front-loads the resource and ordering; the second adds actionable next steps. Every word earns its place.

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 simple read-only list tool with one optional parameter, the description covers what the tool returns and how to use the results. Lacking an output schema, it doesn't describe response structure, but the mention of URIs gives a hint. Minor gaps remain around pagination or account scoping, but overall adequate.

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 schema description for the 'account' parameter is 100% complete, so the schema carries the full parameter documentation. The tool description doesn't add further parameter meaning; it repeats 'connected account' context already implied by the parameter description. Baseline 3 applies.

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 states a specific verb ('list') and resource ('feeds and lists pinned to a connected account's home screen'), and mentions ordering. It also hints at downstream usage with get_feed/get_list_posts, which helps distinguish it from other feed-related tools, though it doesn't explicitly contrast with sibling tools.

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 implies usage context by suggesting to pass returned URIs to get_feed or get_list_posts, but it doesn't state when to choose this tool over alternatives or when not to use it. The guidance is implicit rather than explicit.

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