titan_list_docs

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

No annotations are provided, so the description carries the full burden. It only states that the tool returns a list of topics, which is essentially what the name implies. It does not disclose the return format, whether ordered, pagination, authorization requirements, or any other behavioral trait beyond the basic action.

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 short phrase with no wasted words. It is appropriately brief for a zero-parameter tool, though it could arguably be more structured (e.g., a complete sentence) but this does not detract significantly.

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 has no parameters and no output schema, the description should at least explain what the return value contains. It does say 'list of topics', which gives a general idea, but it does not specify whether the list contains just titles, identifiers, or additional metadata. It is a minimum viable description but lacks detail for an agent to fully anticipate the response.

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 tool has zero parameters, and the input schema is empty with 100% schema description coverage. Since there are no parameters to describe, the description does not need to add parameter-level meaning. The baseline of 4 is appropriate.

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 'Список тем документации Titan SDK.' translates to 'List of topics of Titan SDK documentation.' It clearly indicates the tool lists documentation topics, and this is distinct from sibling tools like titan_get_doc (retrieve a specific doc) and titan_search_docs (search docs). However, it uses a noun phrase rather than an explicit verb, and does not detail the scope (e.g., all topics vs. filtered).

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention that users might first list topics before calling get_doc or search_docs, nor does it state any exclusions or prerequisites. The description simply says what it does without context.

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