getMyAccount

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

No annotations are present, and the description fails to disclose any behavioral traits such as return format, authentication requirements, side effects, or data scope. With no annotation support, the description provides no transparency beyond the tool name.

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 extremely brief (three words), but brevity here results in under-specification rather than effective conciseness. It fails to pack necessary information into the limited space provided.

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 complexity of a tool that likely retrieves account data, with no output schema, no annotations, and incomplete parameter documentation, the description is wholly inadequate. The agent cannot reliably select or invoke this tool based on this information.

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 input schema has a nested object 'pathParams' with a 'format' enum (json/xml), but the description offers no explanation of this parameter. Since schema description coverage is 0%, the description should compensate, but it does not, leaving the agent uninformed about required inputs.

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' vaguely indicates the tool's purpose but is ambiguous; it does not clarify what 'account' refers to (e.g., current user's account or a specific user). Among siblings like 'getCurrentUser', 'getUser', and 'getUsers', there is no differentiation, making it unclear when to use this tool over others.

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 usage guidelines are provided. The description lacks any indication of when to use this tool versus alternatives like 'getCurrentUser' or 'getUser', nor does it mention prerequisites or context.

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