clockodo_list_users

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful context about scope ('all users') and return fields, but it does not clarify pagination behavior even though the schema exposes a 'page' parameter. No contradiction with annotations.

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?

A single sentence that is efficient, front-loaded, and contains no filler. It communicates the core action, target resource, and key return fields without redundancy.

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 is simple, but the undocumented 'page' parameter is a real gap. The phrase 'all users' is ambiguous when a pagination parameter exists, and the lack of an output schema means the description should clarify expected results beyond 'ids and roles'. The definition is too thin to be fully reliable for correct invocation.

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, 'page', has no schema description and schema description coverage is 0%. The description also does not mention the parameter at all, so the agent receives no semantic information about how pagination works or what 'page' means.

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?

Description uses a specific verb ('Lists'), identifies the resource ('all users (team members)'), and states the returned fields ('ids and roles'). It is easily distinguishable from sibling tools like clockodo_list_entries or clockodo_list_customers, which target different resources.

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 implies usage when you need all users and their roles, but it does not explicitly mention alternatives or when not to use this tool. Among the siblings, clockodo_me is the closest alternative for user info, but no routing guidance is given.

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