stellaris_outline

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

With no annotations, the description does carry the burden, and it does disclose the cost hint ('cheap') plus what is returned (section headings). It says nothing about behavior for missing/ambiguous page titles, heading depth or ordering, or how expensive the call actually is relative to alternatives.

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 short sentences, zero waste, with the action front-loaded and the cost/rationale second. Nothing redundant or padded.

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 one-parameter read-only listing tool with no output schema, the description covers what it does and why to call it. The remaining hole is the 'title' identifier format, which matters for correct invocation but is a modest omission overall.

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 0% and the single required parameter 'title' is never explained: the description only says 'of a page', leaving open whether the title must be exact, case-sensitive, or a path/slug. This is a real gap given the schema supplies no help.

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 concrete verb and resource: list the section headings of a page. The phrase 'before reading it' implicitly contrasts with stellaris_get_page, so an agent can distinguish this from a full-page fetch without naming the sibling outright.

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?

'Cheap way to see what a big page contains before reading it' gives a clear when-to-use condition (large pages, triage before full read) and implies the alternative is reading the whole page. It stops short of explicit exclusions, such as when an outline is unnecessary for small pages.

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