Etsy-Anmeldestatus prüfen

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

With no annotations provided, the description carries the full burden. It adds transparency by stating 'ohne Tokens preiszugeben' (without revealing tokens), which is a key behavioral guarantee. It also indicates what the tool reports (scope and expiry), providing useful context. However, it does not explicitly state that the operation is read-only or non-mutating, though the verb 'zeigt' implies it.

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 main action (showing login status), then adds key details (no token leakage, scope, expiry). Every phrase earns its place 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?

The tool has no output schema, so the description must explain what is returned, which it does (status, scope, expiry). It also mentions the privacy aspect. It does not describe error behavior or what happens when no login exists, but for a simple status check, the coverage is adequate.

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 tool has zero parameters, so the baseline is 4. The description adds value by explaining what the output contains (status, scope, expiry), which is more relevant than parameter semantics in this case. Schema coverage is trivially 100% as there are no parameters to document.

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 tool's function: 'Zeigt, ob gerade eine gültige Etsy-Anmeldung besteht' (shows whether a valid Etsy login currently exists). It also specifies the output includes scope and expiry time. This distinguishes it from sibling tools like etsy_auth_login and etsy_auth_logout, which perform actions rather than report status.

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 implies the tool is used to check login status before other operations, but it does not explicitly state when to use it versus alternatives or provide exclusions. While the context is clear given the sibling auth tools, there is no direct guidance on usage scenarios or prerequisites.

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