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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds useful mode-specific behavior—'with its sheets' for slug and 'filterable by name' for public listings—but does not disclose pagination, sorting, or how limit applies.

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?

A single, well-structured sentence communicates the core purpose and all three usage modes without filler. The alternatives are separated by semicolons, making the branching logic easy to parse and front-loaded.

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 is reasonably complete for a read-only browse tool, but it lacks key invocation details with no output schema and four undocumented parameters. It does not explain the precise semantics of contains, how limit interacts with collections vs sheets, or the response shape beyond a loose mention of sheets.

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%, so the description must compensate. It explains slug and user_id clearly, and hints at the contains parameter via 'filterable by name,' but it never names contains explicitly and says nothing about limit or its default/maximum behavior.

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 and resource: 'Browse collections of source sheets.' It also clarifies the three invocation modes—slug, user_id, or neither—making the tool's purpose immediately identifiable. This is specific enough to distinguish it from generic browsing or listing 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?

It provides clear context for when to use each calling mode: pass slug for one collection, user_id for a user's collections, or neither for public collections. However, it does not explicitly compare against sibling tools like browse_library or list_source_sheets, nor state when not to use this tool.

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