list_csdk_topics

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

With no annotations provided, the description carries the full burden. It accurately describes the operation as listing categories and files, which implies a read-only action with no side effects. While it does not detail output format or limitations, for a simple list tool this is adequate and concise.

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 sentences, front-loaded with the action('List all available...') followed by a usage note. Every word serves a purpose and there is no 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 the tool's simplicity (no parameters, no output schema, no annotations), the description adequately explains what it does and why to use it. It is complete enough for an agent to select and invoke it correctly in the context of browsing or searching documentation.

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 input schema has zero parameters, so there is nothing to describe. Per the rubric, the baseline for no-parameter tools is 4, and the description adds context about understanding the documentation structure, which is helpful.

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 the tool lists all available documentation categories and files, and explicitly positions it as a precursor to browsing or searching, distinguishing it from sibling tools search_csdk_docs and browse_csdk_docs.

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 says 'Use this to understand the documentation structure before browsing or searching,' which provides explicit when-to-use guidance and implies the alternatives (browse and search tools). This gives clear context for selecting this tool first.

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