Get Konseki Analysis

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

No annotations are provided, so the description must bear the full burden. It only states 'Fetch raw analysis JSON' but does not disclose behavioral traits such as whether the operation is read-only, destructive, requires authentication, or has rate limits. No additional behavioral context beyond the basic purpose.

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 clear sentence with no extraneous text. It is efficiently front-loaded, though it could benefit from additional structure (e.g., noted parameter details).

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 lack of annotations and output schema, the description is insufficient. It does not explain the return format, error conditions, or provide examples. For a tool with three required parameters and no additional metadata, more context is needed for an agent to use it effectively.

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 description mentions the three parameters (symbol, exchange, lookback) but does not explain their meaning, constraints, or examples. The schema lacks descriptions (0% coverage), and the description adds minimal semantic value beyond naming the parameters.

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 'Fetch raw analysis JSON for a symbol, exchange, and lookback', specifying the verb, resource, and key parameters. It distinguishes from sibling tools 'get_konseki_metadata' and 'list_konseki_symbols' by focusing on raw analysis data.

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 on when to use this tool versus alternatives. The description does not mention the sibling tools or provide any context about when to prefer this over get_konseki_metadata or list_konseki_symbols.

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