auth_login

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

With no annotations, the description carries the full burden of disclosure. It says 'get instructions' but doesn't explicitly state that this operation is read-only, makes no state changes, or what the response format is. The name 'auth_login' could mislead an agent into expecting an active login action.

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?

Single sentence, no filler, front-loaded with the core action. Exceptionally concise.

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 tool with a single optional parameter and no output schema, the description is minimal. It lacks context about how instructions are returned (e.g., a URL, steps), how the provider parameter affects the instructions, or the relationship to other auth tools. Adequate but with gaps.

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 covers the lone parameter (provider) with options and default, so the baseline is 3. The tool description adds minimal semantic value beyond the schema, just indicating the provider is for image generation.

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 provides authentication instructions for an image generation provider, using a specific verb ('get') and resource. It distinguishes from siblings like auth_status (check status) and auth_logout (end session) by focusing on instructions, though it doesn't mention what form the instructions take.

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 guidance is provided on when to use this tool versus auth_status or auth_logout. The description doesn't mention prerequisites (e.g., need an account) or alternative scenarios, leaving the agent to infer usage.

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