list_saved_posts

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

Without annotations, the description carries the burden. It discloses that the tool lists 'cached' posts, indicating the data may not be real-time, a key behavioral trait. It also explains sort_by semantics and audience tier filtering. It stops short of describing potential staleness or error behavior, but the core behavioral context is present.

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 sentences, all information-dense. The first sentence states the primary purpose, the second and third explain specific parameters. No filler or redundant 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?

With an output schema present, return values are covered. The description covers pagination, filters, sort options, and refers to a sibling tool for audience values. It could mention when to use this vs search_saved_posts, but overall it is sufficient for an agent to invoke 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?

Schema has 0% property descriptions, so the description is the only source. It explicitly explains sort_by (saved_at vs published_at) and audience (tier values, referencing list_audiences). Publication is only mentioned as a filter without valid values, and limit/offset are left to schema defaults. Despite these gaps, it adds substantial meaning for the key parameters.

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 opens with a specific verb 'List' and resource 'cached saved posts', clearly distinguishing it as a browsing tool from siblings like get_saved_post (single item) and search_saved_posts (search). It also hints at optional filters, which further narrows the tool's scope.

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 provides clear context for use: pagination and optional filters for publication/audience. It gives concrete guidance for sort_by values and cross-references list_audiences for valid audience filters. However, it does not explicitly mention alternatives or when not to use this tool (e.g., when a full-text search is needed).

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