browse_collection

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

No annotations are provided, so the description carries full burden. It mentions browsing by section and type but doesn't disclose key behaviors like whether this is a read-only operation, if it requires authentication, what the output format is, or any rate limits. This leaves significant uncertainty for an agent.

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 appropriately concise with two sentences that directly address the tool's function. It front-loads the core purpose and adds a clarification about 'personas', with no wasted words, though it could be slightly more structured for optimal clarity.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., list of items, metadata), how results are formatted, or any behavioral constraints. For a browsing tool with 2 parameters, this leaves the agent under-informed about execution outcomes.

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 already documents both parameters thoroughly. The description adds minimal value by listing content types and clarifying 'personas', but doesn't provide additional semantics beyond what's in the schema descriptions, resulting in a baseline score.

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 clearly states the tool's purpose: 'Browse content from the DollhouseMCP collection by section and content type.' It specifies the verb (browse) and resource (DollhouseMCP collection). However, it doesn't explicitly differentiate from sibling tools like 'search_collection' or 'get_collection_content', which limits the score.

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 some implied usage context by mentioning content types and clarifying that 'personas' refers to a specific type. However, it lacks explicit guidance on when to use this tool versus alternatives like search tools or when parameters are required, leaving gaps in decision-making.

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