getMyAccount

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

The readOnlyHint annotation already indicates this is a read-only operation, and the description's verb 'show' aligns with that. However, the description adds no additional behavioral context, such as authentication requirements, rate limits, or return format specifics, beyond what the annotation provides.

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 short sentence, which is concise and front-loaded. However, it is under-specified to the point of being insufficient, trading depth for brevity, so it is not optimally structured for the tool's informational needs.

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 tool's simplicity (one parameter, no output schema), the description is incomplete: it does not explain the format parameter's role, clarify what 'my account' entails, or describe the expected response structure. The agent would be left with significant gaps for correct invocation and interpretation.

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 pathParams with a required format enum (json/xml), but the description does not explain the purpose or impact of this format parameter. With 0% schema description coverage, the description carries the full burden of parameter explanation but fails to provide any, leaving the agent to guess what 'format' controls.

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 'Show my account' uses a specific verb and resource, clearly indicating it retrieves the current user's account information. However, it does not differentiate it from sibling getCurrentUser, which likely serves a similar purpose, so it lacks sibling differentiation.

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 provides no guidance on when to use this tool or how it differs from alternatives like getCurrentUser or getUsers. No context on typical use cases or prerequisites is given, leaving the agent to infer appropriateness.

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