browse_collection

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Browse' implies a read-only operation, but the description doesn't confirm this, nor does it detail aspects like pagination behavior (implied by offset/limit), rate limits, authentication requirements, or error handling. It lacks critical behavioral context for safe and effective use.

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 a single, clear sentence with no wasted words, making it easy to parse. However, it's front-loaded but lacks depth, as it doesn't elaborate on key aspects like output or usage, which could be addressed with slightly more detail without sacrificing conciseness.

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?

Given the tool has 4 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what 'browse' returns (e.g., list of items, metadata), behavioral traits like pagination or errors, or how it fits among siblings. For a read operation with multiple parameters, this leaves significant gaps for the agent.

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%, so the schema fully documents all parameters (collection_id, sort, limit, offset). The description adds no additional meaning beyond the schema, such as explaining what 'browse' returns or how parameters interact. This meets the baseline of 3, as the schema handles the heavy lifting.

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 'Browse content within a specific collection' clearly indicates the action (browse) and target (content in a collection), but it's vague about what 'browse' entails (e.g., listing items, viewing metadata) and doesn't distinguish it from siblings like 'browse_libraries' or 'browse_library', which likely have similar browsing functions for different resources.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., authentication), compare it to siblings like 'browse_libraries' or 'search_plex', or specify use cases (e.g., exploring a collection vs. searching). Without such context, the agent must infer usage from the name alone.

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