login

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

No annotations are provided, so the description carries the full burden. It discloses opening a browser, performing PKCE flow, and saving a config file. However, it does not mention side effects (e.g., overwriting existing config), whether the tool blocks, or security implications. Adequate but not exhaustive.

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?

One sentence with no wasted words. It efficiently conveys the main action (authentication) and key detail (config file location).

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 simple tool with one optional boolean parameter and no output schema, the description covers the process (browser, PKCE, config save) and parameter behavior. It lacks mention of return value or error cases, but these are implied given the tool's nature.

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 description coverage is 100% (one parameter with description). The description does not add meaning beyond the schema; it repeats the parameter's purpose. 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?

The description clearly states it authenticates RunAPI via a PKCE login flow and saves the API key to a specific config file. The verb 'Authenticate' and resource 'RunAPI' are specific, and the method (browser PKCE flow) distinguishes it from sibling tools which are unrelated (animate, check_pricing, etc.).

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 for authentication before other tools, but it does not explicitly state when to use it versus alternatives, nor does it provide exclusions or prerequisites. Given no sibling overlaps, it's adequate but lacks explicit guidance.

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