titan_get_spec_data

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

With no annotations provided, the description carries the burden. It discloses an important behavioral trait: for healers, APL is unavailable and returns apl_available=false, with a specific exception. It also discloses the numeric-ID constraint. However, it doesn't explicitly state read-only nature or side effects like caching, but the schema description for resolve_ids does cover the DB2 download.

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 main purpose and followed by a crucial caveat. Every clause adds value; 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?

The tool has no output schema, but the description explains what is returned (APL + numeric spell IDs) and key edge cases. It doesn't detail return structure but given the caveats, it is sufficiently complete for an AI agent to select and invoke correctly.

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?

Schema description coverage is only 33% (only resolve_ids has a description). The main description mentions 'for class/spec' but doesn't provide format or examples for class/spec. It adds context that healers are treated specially, which relates to the spec parameter, but does not fully compensate for the undocumented params.

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 explicitly states the tool returns 'SimC APL (conditional priority) + numeric spell IDs for class/spec', which is a specific verb+resource. It also distinguishes from the sibling titan_get_role_blueprint by noting when APL is unavailable for healers, that alternative should be used.

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 provides explicit when-to-use guidance: for healers (except druid_restoration), APL doesn't exist and apl_available=false, so 'you need to use titan_get_role_blueprint'. It also states Titan only works with numeric IDs, implying prerequisites. This is clear and actionable.

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