get_account_users

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

The description lacks annotations like readOnlyHint or destructiveHint. While 'Lists' implies a read operation, it does not disclose other behaviors such as pagination, sorting, or response format. The description minimally covers transparency beyond the annotation openWorldHint.

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 with no redundancy or unnecessary words. It efficiently conveys the tool's purpose.

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 with no parameters and no output schema. The description tells what it does but omits details about the return format (e.g., list of user objects). It could be slightly more complete by hinting at the output structure.

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?

With zero parameters, the schema provides all necessary structural info. The description adds valuable context by clarifying 'for the current account', which indicates the account is determined by authentication. This exceeds the baseline expectation for 0-parameter tools.

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 uses a specific verb 'Lists' and resource 'account users', clearly indicating the tool's function. It distinguishes itself from siblings like create_contact, get_proposal_templates, etc., which are unrelated to listing 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 explicit guidance on when to use this tool versus alternatives. However, the sibling tools cover different domains (contacts, proposals, templates), implying this is the go-to for account users. Usage context is implied but not stated.

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