Log in and obtain an auth token

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

Discloses auto-detection, field variant attempts, and token extraction. However, lacks details on failure modes, side effects, or prerequisites beyond credentials. No annotations to supplement.

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 cover the core functionality efficiently, front-loaded with actionable information. No extraneous text.

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 7 parameters and no output schema or annotations, the description is adequate but lacks details on return format, error handling, and what 'reports exactly what worked' means.

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 has 100% parameter descriptions, so baseline is 3. Description adds process context but does not enhance individual parameter meanings beyond schema.

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 title and description clearly state the tool logs in and obtains an auth token. It specifies auto-detection of login endpoint, credential field variants, and token extraction. Different from sibling tools like detect_base_url or scan_endpoints.

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?

Description implies usage when base URL and credentials are available, but does not explicitly state when to use or when not to, nor provide alternative tools. No direct comparison with siblings.

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