zeppelin_login

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

Discloses that it stores a session cookie for subsequent requests, which is a key behavioral trait beyond input schema. No annotations provided, so description carries full burden – adequately covers side effects.

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, no waste, front-loaded with action. 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 simple auth tool with no annotations and no output schema, the description covers purpose, prerequisite, and effect. Sibling tools are different enough that context is clear. Minor gap: no mention of error handling or token expiry.

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 100% – both parameters are described. Description does not add extra meaning beyond what the schema provides, so 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 the verb (authenticate), resource (Apache Zeppelin), and purpose. Distinguishes from sibling tools which are about notebook/paragraph operations.

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 states 'Must be called before any other tools' – clear guidance on when to use it. No alternatives or exclusions listed, but for an auth tool this is sufficient.

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