Get user

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

No annotations are provided, so the description carries the full behavioral burden. It does not state whether the call is read-only (implied only by the name), what happens if accountId doesn't exist, what permissions are needed, 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?

It is a single terse fragment with zero filler, so it is front-loaded, but the brevity comes from under-specification rather than efficiency. One more sentence on return shape or ID expectations would have earned its place.

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?

For a simple one-parameter read tool this could be complete with one clarifying clause, but the description says nothing about the returned user object, error behavior on unknown IDs, or how it relates to sibling user tools. With no annotations and no output schema, too much is left implicit.

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?

Schema description coverage is 100% — the single accountId parameter is documented as "ALSO Cloud Account ID" — so the schema does the heavy lifting. The description adds nothing beyond repeating that the lookup is by accountId, matching the baseline 3 for full schema coverage.

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?

"GetUser — user by accountId" largely restates the tool name and title, adding only that the lookup key is accountId. It does not distinguish this single-user fetch from the sibling get_users (plural list) or explain what a 'user' record contains.

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?

There is no guidance on when to use this instead of get_users, update_user, or get_company. The agent must infer that this is the single-record lookup by ID purely from the name.

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