stellaris_get_page

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

With no annotations, the description must carry behavioral load. It discloses that this is a read from the local KB and that output is full page text unless narrowed, which establishes safety and scope. It omits anything about missing titles, truncation behavior, or size limits, which the schema only partly covers.

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 filler, with the core action front-loaded and the optional scoping behavior second. Nothing is wasted.

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 3-parameter read tool the description is adequate: it names the source and the return payload. However, with no output schema and no annotations, it should say what happens on a missing or ambiguous title and that output is truncated by default.

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 100%, so the parameters are already documented, and the description adds no syntax, matching rules, or format guidance beyond restating section narrowing. Baseline 3 applies.

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 ('Fetch') and resource ('full text of a wiki page') plus the source ('local KB'), which implicitly separates it from stellaris_live_fetch. It does not explicitly name a sibling, so it falls short of full differentiation.

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?

Usage is only implied: 'local KB' hints at when to prefer this over a live fetch, and 'Optionally narrow to one section' hints at a cheaper scoped read. There is no explicit when-to-use or when-not-to-use versus stellaris_search or stellaris_live_fetch.

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