pipedrive_users_list

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

Without annotations, the description must disclose behavioral traits. It states 'List all' but does not mention pagination, limits, or the effect of the active_flag parameter. The agent gains no insight into behavior beyond a simple fetch.

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?

While the description is very short (6 words), it is under-specified and omits crucial details about the parameter and any caveats. Conciseness should not sacrifice essential information.

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?

The tool has a simple schema and no output schema, so the description could be brief but it should still mention the parameter's meaning and that it lists all users. It lacks completeness for even a trivial 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?

The only parameter (active_flag) has no description in the schema, and the tool description does not mention it at all. With 0% schema description coverage, the description fails to add any semantic value for the parameter.

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 action (list) and resource (all Pipedrive users in the account), making the tool's purpose immediately understandable. However, it does not distinguish from sibling tools like pipedrive_users_get or pipedrive_users_permissions, but the name itself is sufficient given there is no other list-all tool for users.

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 such as pipedrive_users_get for a single user or pipedrive_users_permissions for permission details. The description lacks usage context or exclusions.

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