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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds specific data fields returned (profile, reputation, etc.) and clarifies it pertains to the authenticated seller. However, it does not discuss potential rate limits, authorization requirements beyond 'connected', or nuances like account selection. With annotations covering safety, this is adequate but not extensive.

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 concise sentence that front-loads the core action and data. It avoids fluff. However, it omits parameter clarification, which is a significant gap, but the conciseness itself is good.

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 there is no output schema and only 1 parameter with 0% description coverage, the description should describe what the tool returns and how the parameter works. It only lists data categories, not the parameter, nor any prerequisite like 'requires a connected account'. It is moderately complete for a simple GET, but lacks essential parameter guidance.

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?

There is one optional parameter 'account', but the description does not explain its purpose or format. Schema coverage is 0%, so the description should compensate, but it completely omits parameter information. The agent cannot infer whether this is an account ID, name, or something else.

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 purpose: retrieving data of the connected seller account (GET /users/me), and lists specific data fields (profile, reputation, site, account type, seller status). It distinguishes itself from siblings like mercadolivre_get_user (which may fetch a different user) by specifying 'vendedor conectado'.

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 explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites, such as authentication, nor does it compare with related tools like mercadolivre_get_user. The description is purely declarative without usage context.

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