skypilot_api_logout

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

Annotations supply destructiveHint=true, and the description earns credit beyond that by disclosing exactly what is destroyed ("Clears all cookies and settings") and the precondition (remote servers only). It still doesn't say whether the operation is reversible or what happens if called against a local server, but the added context is substantive.

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?

Three short sentences with zero filler; purpose and the destructive effect are front-loaded, and the precondition is held to the end where it belongs.

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?

An output schema exists so return values need no explanation, and annotations cover the safety profile. The description covers purpose, effect, and precondition; only the failure/edge behavior (e.g., calling it against a local server) is unaddressed, which is a minor gap for a no-arg session tool.

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?

Zero parameters, so the baseline is 4. There is nothing for the description to disambiguate in the schema, and it correctly avoids inventing parameter detail.

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?

States a specific verb+resource ("Log out of the remote SkyPilot API server") and adds a scope qualifier ("Only works for remote API servers"). An agent can immediately distinguish this from the sibling skypilot_api_login without opening the schema.

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 gives an implied usage condition ("Only works for remote API servers") which is useful, but never names the counterpart tool (skypilot_api_login) or states when an agent should prefer logout vs. other session-ending operations. Adequate but leaves routing to inference.

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