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 the tool's role in obtaining access tokens and its prerequisite status, but it doesn't mention token expiration, security considerations, or potential errors. This adds some behavioral context beyond the schema but leaves room for more detail.

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, focused sentence that immediately states the tool's purpose and its prerequisite status. Every word is useful, and no unnecessary information is included.

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 is simple, and the description covers its main purpose and usage. Although there is no output schema to explain the response structure, the fact that it returns access tokens is clearly stated. It could mention that the tokens should be used in subsequent calls, but that is implicit from 'Required before using other endpoints'.

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 input schema provides 100% coverage with descriptions for all three parameters, including the optional deviceId. The description doesn't repeat parameter details, which is appropriate since the schema already handles this. Baseline score of 3 applies because no additional parameter semantics are needed.

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 identifies the tool as the authentication endpoint using the verb 'Authenticate' and specifies the resource 'MyWhoosh'. It explicitly states it returns access tokens, which distinguishes it from all sibling tools that perform CRUD or query 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?

The description provides explicit guidance that login is 'Required before using other endpoints', which tells the agent when to invoke it. It doesn't mention alternatives, but no alternatives exist among siblings, so this is still clear usage context.

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