List Colyseus documentation pages

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

With no annotations, the description carries full burden. It discloses return fields (slug, title, category, one-line description) and notes that slug is used for read_doc. It could mention ordering or pagination, but for a parameterless list tool, the transparency is good.

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 a single paragraph of three sentences, each earning its place: main action, details of return value, usage guidance. It is front-loaded and free of fluff.

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 parameters, no output schema, and the presence of siblings read_doc and search_docs, the description is complete enough. It covers what the tool does, what it returns, and how to use the results. Minor gaps (e.g., error handling, sorting) are acceptable for a simple list.

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?

No parameters exist, so schema coverage is 100%. The description adds value by explaining that the slug field is meant to be used as the slug argument to read_doc, beyond just listing fields.

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 'List every Colyseus documentation page available to this MCP server,' specifying the verb (list), resource (documentation pages), and scope (every page). It distinguishes from siblings read_doc (reads a specific page) and search_docs (searches).

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 explicitly says 'Use this first to discover what topics are covered before reading individual pages,' providing clear when-to-use guidance and implicitly contrasting with read_doc and search_docs.

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