list_available_topics

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

No annotations provided; description does not state that the operation is read-only or mention any side effects, limits, or authentication needs. For a listing tool, additional behavioral context is expected.

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?

Description is slightly verbose with bullet points but remains focused. Information is front-loaded with the core purpose. Could trim the internal memo style but is adequate.

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 zero parameters and no output schema, the description provides a reasonable overview of the output categories. However, lacks details on pagination, size limits, or exact response format, leaving some gaps.

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 in schema (100% coverage). Description adds value by detailing the categories of returned information (troubleshooting, admin, SPL commands, URI patterns, version support), though no param details are needed.

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?

Clearly states it lists all available documentation topics and URI patterns for discovery. Distinguishes from sibling tools like list_admin_topics by being a broader discovery tool, as emphasized in the description.

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?

Explicitly advises to 'Use this tool first to discover what documentation is available before requesting specific topics,' providing clear when-to-use guidance and suggesting it as a precursor to other documentation tools.

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