get_collection_roles

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

No annotations are provided, so the description carries full burden. It states 'Get roles' which implies a read-only operation, but doesn't disclose behavioral traits such as authentication requirements, rate limits, pagination, or error handling. For a tool with no annotations, this leaves significant gaps in understanding how it behaves.

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. It's front-loaded and efficiently conveys the core purpose without unnecessary elaboration, making it easy to parse quickly.

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 'roles' includes (e.g., permissions, user assignments), the return format, or error cases. For a tool that likely returns structured data about roles, more context is needed to understand its full functionality.

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?

The input schema has 100% description coverage, with 'collectionId' documented as 'The collection ID'. The description doesn't add any meaning beyond this, such as format examples or constraints. With high schema coverage, a baseline score of 3 is appropriate as the schema handles parameter documentation adequately.

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 'Get roles for a collection' clearly states the action (get) and target (roles for a collection), which is adequate. However, it doesn't differentiate from sibling tools like 'get_workspace_roles' or 'list_workspace_roles', leaving ambiguity about scope. The purpose is understandable but lacks specificity about what 'roles' entail in this context.

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?

No guidance is provided on when to use this tool versus alternatives. With siblings like 'get_workspace_roles' and 'list_workspace_roles', the description doesn't clarify if this is for collection-specific roles, workspace-level roles, or other distinctions. There's no mention of prerequisites or context for usage.

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