identify_user

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

Since no annotations are provided, the description must disclose behavior. It does indicate that the tool reads from the current credentials, implying a read-only operation, but it does not state prerequisites such as needing an active session or what happens if credentials are invalid. The 'Call this first' instruction adds some behavioral context but leaves gaps.

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 two short sentences that immediately state the action and the recommended usage order. Every word earns its place, with no redundancy or filler.

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 zero-parameter schema and lack of an output schema, the description provides the essential information: what the tool lists and when to call it. It could be enhanced by explicitly stating whether a prior session initialization is required, but overall it is adequate for a simple discovery 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 tool accepts no parameters, and the input schema is empty. With zero parameters, the baseline is 4, and the description correctly omits parameter details, focusing on the tool's purpose instead.

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 ('List') with a clear resource ('Anaplan workspaces') and scope ('accessible to the current credentials'). It distinguishes from siblings like list_accessible_models by focusing on workspaces rather than models, and adds a usage hint with 'Call this first'.

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 explicitly states when to use the tool: 'Call this first to understand what the user can see.' This establishes the tool as an initial discovery step. However, it does not mention alternatives or when not to use it, so it stops short of a full usage guide.

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