set_online

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

The description adds detail about the 'offline' parameter, explaining that it toggles the green online indicator. However, it does not disclose other behavioral aspects such as authentication requirements or the effect of setting offline to false, and relies on annotations for mutation semantics.

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 concise, with a clear purpose statement and a parameter explanation. No unnecessary words.

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 one-parameter tool, the description covers the essential operation and parameter meaning. It doesn't discuss the online=true case explicitly but it's easily inferred. The presence of an output schema further reduces the need for return-value documentation.

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 single parameter 'offline' is explicitly explained in the description with a concrete behavioral consequence (hiding the green 'online' circle). This compensates for the lack of schema descriptions.

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 the tool's function: setting the user's online/offline status. It uses a specific verb and resource, and it distinguishes itself from sibling tools by focusing on presence status.

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?

No guidance is provided about when to use this tool versus alternatives, nor any context for its use. The description only states what the tool does and explains the parameter, but offers no usage direction.

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