titan_get_doc

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

No annotations are provided, so the description must carry the disclosure burden. It only says 'full documentation' without explaining return format, errors, or side effects. The example topics add context but do not reveal expected behavior.

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 concise sentence, front-loaded with the purpose. It contains no redundant words and is easy to parse. It could include more detail without becoming verbose, but as is it is appropriately sized.

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?

The tool has one parameter, no annotations, and no output schema. The description gives minimal information about the tool's behavior, not clarifying what the returned documentation looks like, possible errors, or any prerequisites. Given the lack of structured metadata, the description is insufficient for complete understanding.

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 has no description for 'topic' (0% coverage). The description compensates by listing example values (aura, spell, player, group…), giving some indication of valid inputs. However, it does not specify an exact enumeration or format, leaving partial ambiguity.

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 action (get documentation) and the resource (topic), with examples like aura, spell, player, group. It distinguishes from siblings such as titan_list_docs and titan_search_docs by focusing on retrieving full docs for a specific topic.

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 usage: when you need full documentation on a given topic. However, it does not explicitly mention when to prefer this over titan_search_docs or titan_list_docs, and lacks any exclusion criteria or alternative guidance.

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