what_should_i_do_tonight

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

With no annotations provided, the description carries the behavioral disclosure burden. It explains it uses the logged-in character's skillpoints, wallet, location security, current ship, and training queue, and that it returns building blocks rather than final suggestions. This is useful behavioral context, though it omits details like response format or potential errors.

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 three sentences and every sentence adds relevant detail: what the tool does, what it returns, and the login requirement. It is appropriately sized, though it could be tightened slightly.

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?

Given no output schema and no annotations, the description does a solid job explaining the tool's inputs, process, and output nature. It clarifies that output is raw building blocks for the agent to turn into suggestions, which is essential for correct invocation. It lacks some edge-case detail but is reasonably complete for a zero-parameter 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?

The tool has zero parameters, so the baseline is 4. The description adds useful semantics by explaining what data the tool composes internally, which compensates for the lack of input schema.

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 answers the question 'what should I actually do right now?' by composing the character's situation with income options. It identifies the resource (the logged-in character's current state) and distinguishes itself from siblings by generating session suggestions rather than just providing data.

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 clear context for when to use it: when the user asks for immediate activity suggestions. It also notes a prerequisite (requires login) but does not mention alternative tools or exclusions, so it stops short of a full 5.

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