parse_list_roles

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

With no annotations provided, the description carries the burden. It discloses the master key requirement and filtering behavior, but does not describe the return format, pagination behavior, or explicitly confirm it is read-only. This is moderately transparent.

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 concise sentence that front-loads the main purpose, includes an example, and mentions the key prerequisite. No wasted words.

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?

For a list tool with simple semantics, the description covers the essential behavior (list all, filter, limit, master key). It lacks return format details, but given no output schema, this is a minor gap.

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 description explains the 'where' filter with a concrete example and clarifies that 'limit' restricts results. Since the schema has 0% coverage for the actual parameter (inputSchema), the description compensates well by explaining the nested fields.

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 lists all roles in Parse Server, with optional filtering and limit. This distinguishes it from siblings like parse_get_role (single role) and parse_list_users (different resource).

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 mentions the master key requirement and optional filtering/limit, providing context for use. However, it does not explicitly differentiate this tool from parse_get_role or specify when to use this vs alternatives.

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