browse_collection

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions pagination behavior (page, default 10 posts per page) but does not cover authentication needs, error handling, or side effects. This is insufficient for a tool with no annotations.

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 concise, consisting of three short sentences in a standard docstring format. Each sentence serves a purpose: purpose, parameters, returns. No redundant information.

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?

The description covers the tool's operation and parameters adequately for a simple read operation. The output schema exists (as per context signals), so the vague return description 'Formatted list of posts' is acceptable. However, it could mention the format or any limits on the list.

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 0%, meaning the schema provides no parameter descriptions. The description compensates by clearly explaining both parameters: collection_alias as 'the alias/name of the collection' and page as 'page number for pagination (default: 1, returns 10 posts per page)'. This adds significant value beyond the schema.

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?

Description clearly states the tool lists posts in a specific collection/blog. It uses a specific verb 'list' and resource 'posts in a collection', which distinguishes it from sibling tools like browse_public_feed or list_my_collections.

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 when to use the tool (to list posts in a specific collection). However, it does not explicitly mention when not to use it or point to alternatives like browse_public_feed or list_my_posts, which are provided in sibling tools.

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