adobe_get_user

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

With no annotations provided, the description carries the transparency burden. It discloses a rate limit and that the input can be an email or Adobe username, but it doesn't mention error behavior, permissions, or explicitly state it's a read-only operation (though 'get' implies it). The rate limit adds some behavioral context, but other aspects are missing.

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 concise with three sentences covering purpose, rate limit, and parameter usage. It's front-loaded with the main action and does not include excessive detail, though the rate limit might be optional for tool selection.

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 single-get tool, the description provides the core purpose and a key parameter detail, and the output schema presumably handles return structure. However, it lacks explicit guidance on alternative tools and edge-case behavior, so it's not fully complete.

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 description expands on the schema's bare 'email' parameter by explaining it can be an Adobe username string as well, adding meaningful semantics beyond the schema. This is the only parameter, and the description compensates for the 0% 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?

The description clearly states the tool 'gets a single user's details' with a specific verb and resource, and distinguishes from sibling 'adobe_list_users' by focusing on a single user. The inclusion of 'group/product profile memberships' adds specific scope.

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 the tool is for retrieving one user's information, contrasting with the 'list' sibling tools, but it doesn't explicitly tell the agent when to choose this over others or mention any exclusions. This is implied usage based on the word 'single'.

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