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

The annotations already indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description does not need to restate that this is a read operation. However, it adds no extra behavioral context such as authentication requirements, account scoping, or what the response contains.

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 very short and front-loaded, but 'Get User Info' and 'Gets information about the user' are largely redundant. The brevity is fine, but the repeated content takes space that could have been used to explain the account parameter or distinguish this tool from siblings.

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?

There is no output schema, so the description should clarify what 'user info' includes, but it does not. The tool also has an unexplained optional account parameter and sits among many similar user/account-related tools, making the description insufficient for full context.

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 schema has one parameter, 'account', with no description, and schema description coverage is 0%. The description never mentions this parameter, so the agent is left to guess whether 'account' is an ID, email, workspace identifier, or whether omitting it returns the current user.

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 tool gets information about the user, using the verb 'get' with the resource 'user info.' It is understandable on its own, though it does not differentiate from sibling tools like elevenlabs_get_user_subscription_info or elevenlabs_list_accounts.

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 about when to use this tool versus the many related getter tools. There is no mention of alternatives, exclusions, or context such as whether it returns current user info versus subscription or workspace data.

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