Get AK API entry

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

Describes exactly what the tool provides (signature, parameters, return value, etc.) and gives an example. With no annotations, it carries the full burden; it clearly indicates a read-only lookup without side effects.

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?

Single sentence, front-loaded with the list of outputs, includes an example. Every word is valuable and no redundancy.

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?

For a simple single-parameter tool without output schema, the description covers the expected return items comprehensively. It lacks details on result format or error handling, but the provided list is sufficient for typical use.

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 coverage is 100% so baseline is 3. The description adds example symbol names but no additional semantics beyond the schema's 'exact symbol name'.

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 returns exact signature, parameters, return value, semantics, examples, and FATAL codes for an AK symbol. It uniquely distinguishes from siblings like list_ak_api and search_ak_docs by focusing on detailed documentation for a specific symbol.

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 explicit guidance on when to use this tool versus siblings. It doesn't mention that it is best when the exact symbol is known or when detailed info is needed, nor does it exclude cases where search or list would be more appropriate.

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