Get customer profile

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

No annotations are provided, so the description carries the full burden. It conveys that the operation is a read ('Get'), requires authentication via session_id, and is scoped to the logged-in customer. However, it does not mention failure modes, session expiration, or explicitly confirm there are no side effects, leaving some behavioral ambiguity.

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, well-structured sentence that front-loads the resource, includes the key returned fields, and states the required authentication context. Every word contributes necessary information with no redundancy.

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 getter, the description provides the essential context: what is being fetched, for whom, and how authentication is supplied. It names the returned profile fields, partially compensating for the lack of an output schema. It could be slightly more explicit about error or invalid-session behavior, but overall it is sufficiently complete for this tool's complexity.

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%, and the schema already documents session_id as 'The session_id returned by login.' The description reinforces this by saying 'using a session_id from login,' but it adds no new parameter meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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 verb ('Get'), the specific resource ('logged-in customer's profile'), and the fields returned ('name, email, saved addresses'). It also distinguishes itself from siblings by emphasizing the logged-in scope and the session_id requirement, which no other sibling tool mentions.

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 clearly implies this tool is used after login, since it requires a session_id from login and targets the logged-in customer. No explicit alternatives or exclusions are given, but no sibling tool appears to offer the same profile-fetching functionality, so the context is sufficient.

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