market_login

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

Discloses return values (access + refresh tokens), token lifetimes (90d, 365d), local persistence, and auto-refresh behavior on 401. Completely transparent for a login tool with no annotations.

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?

Two sentences, all relevant information succinctly presented. No wasted words; every sentence adds value.

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 login tool with 2 parameters and no output schema or annotations, the description covers purpose, prerequisites, return behavior, token lifetimes, persistence, and error handling. 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?

Schema coverage is 0% and description does not explain parameters beyond their names. While 'username' and 'password' are self-explanatory, the tool has 2 parameters and no additional constraints are mentioned (e.g., required vs optional). Baseline 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?

Clearly states it authenticates in CLI Market and is a prerequisite for cart, checkout, or orders. The verb 'authenticate' and resource 'CLI Market' are specific, and it distinguishes from sibling tools by its role as a gateway.

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?

Explicitly says 'Call before cart, checkout, or orders.' and describes when to re-login vs. rely on auto-refresh after a 401. Provides clear context for when to use this tool over others.

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