parse_list_users

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

With no annotations, the description carries the full burden. It discloses the master key requirement and optional filter/limit behavior. It implies a read-only operation ('lista') but doesn't explicitly state safety or response format, though the master key disclosure adds meaningful context.

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?

Three short sentences, each with clear purpose: main action, optional parameters, and authentication requirement. 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?

Given the simple listing purpose and lack of output schema, the description is mostly complete. It covers the main functionality and required permission. It doesn't describe response shape or pagination, but those are not critical for tool selection. The missing inputSchema nesting detail 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 schema has 0% coverage for the top-level parameter, and the description explains where and limit with an example. However, it doesn't clarify that these values must be nested inside an 'inputSchema' object, which could lead to incorrect invocation. The description adds value but misses the structural nuance.

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 'Lista todos los usuarios' (lists all users), distinguishing it from siblings like parse_get_user and parse_create_user. It also mentions optional filtering and limit, making its scope unambiguous.

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 clear context for use: it lists all users with optional where filtering and limit, and states the master key requirement. It doesn't explicitly compare to alternatives, but the purpose is evident enough to infer when to use it.

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