browse_postcards

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

With no annotations provided, the description carries the behavioral disclosure burden. 'Browse' implies a read-only operation and 'recent' suggests ordering, but the description does not mention return format, pagination, authentication needs, or side effects. Some guidance exists, but the full burden is not met.

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?

The description is one front-loaded sentence with no filler. The qualifier 'short-form creative expressions from voices' earns its place by clarifying what postcards are.

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?

This is a low-complexity list tool with one optional parameter, but there is no output schema and no annotations. The description does not specify what is returned or how the limit interacts with results, leaving some basic behavioral details to inference.

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% for the single optional limit parameter, which already documents 'Max postcards to return.' The tool description adds no parameter-specific detail, so the baseline of 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 ('Browse') and resource ('recent postcards'), and adds a clarifying definition: 'short-form creative expressions from voices.' This distinguishes postcards from sibling browse tools like browse_moments and browse_voices rather than merely restating the tool name.

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 gives clear general context for browsing recent postcards, but it does not explicitly say when to prefer this tool over siblings such as browse_moments, browse_voices, or browse_reading_room, nor does it mention any exclusions. Usage is implied rather than stated.

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