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

With no annotations provided, the description carries the full behavioral burden. It discloses 'No auth' and implies read-only behavior, but it does not specify behavior for invalid slugs, the format of the returned content, or what 'established' means. This is adequate but incomplete.

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 two short sentences with no filler. The primary action is front-loaded, and the 'No auth' detail is isolated for quick scanning. Every word contributes meaning.

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 read tool, the description covers the core calling convention and auth requirement. However, because there is no output schema, the description should have indicated what the tool returns (e.g., page content or metadata), and it does not. The meaning of 'established' is also left undefined.

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 schema already provides 100% coverage for the slug parameter, so the baseline is 3. The description adds value by listing concrete example slug values, helping an agent understand what valid inputs look like. It also reinforces the schema's note about empty input listing all pages.

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 states a specific verb ('Read'), a clear resource ('established wiki page'), and the access method ('by slug'). Concrete example slugs (desk, github, glama, catalog) further clarify the scope. No sibling tool serves the same function, so it is easily distinguishable.

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 implies that the tool is for reading a known wiki page via its slug, and the schema adds that an empty slug lists all pages. However, it does not explicitly discuss when to use this tool instead of alternatives, nor any exclusions. Given there are no wiki-specific siblings, this is a minor but present gap.

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