list_users

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

No annotations provided. Description discloses admin requirement and return structure, but does not mention idempotency, rate limits, or potential errors. Adequate for a read-only list operation.

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 sentences: purpose, constraints, and details. Front-loaded and no redundant information. Efficient.

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?

No output schema, but description includes return type and fields. Missing error conditions or authentication details, but overall sufficient for a simple listing tool.

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 covers both parameters. Description adds context: pagination usage, limit max of 100, and return type (array of user objects with fields). Adds value beyond schema.

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 'List all users in the Langflow instance' with a specific verb and resource. It distinguishes from siblings by focusing on users and is not duplicated among other list tools.

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?

Mentions 'Admin-only endpoint' and describes pagination with skip and limit, but does not explicitly contrast with similar tools like get_current_user or other listing tools.

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