signallord_get_odin_analysis

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

Annotations already mark the tool as read-only and non-destructive. The description adds valuable behavioral context: analysis is cached for ~4 hours and refreshed automatically, and it distinguishes free vs. premium tier content. This goes beyond what annotations provide.

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 well-structured: a clear opening sentence, then contextual detail, caching info, and tier breakdown. Every sentence adds value without redundancy. It is appropriately sized for the tool's simplicity.

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's simplicity (one optional param, output schema exists), the description covers caching behavior and tier differences. It does not explain internal terms like 'gauge data', but that is acceptable for an analysis tool. The output schema fills any return-value gaps.

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 input schema has 0% description coverage for the single optional parameter ('response_format'). The description does not mention this parameter at all, missing an opportunity to explain its purpose or accepted values. For a low-coverage schema, the description should compensate but fails.

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 'Get Odin's current Bitcoin market analysis' and explains what Odin is (AI analyst synthesizing multiple data sources). It uses a specific verb-resource combination, but does not explicitly distinguish from sibling tools like signallord_ask_odin.

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 by describing what the tool returns and notes differences between free and premium tiers. However, it does not explicitly state when to use this tool versus alternatives (e.g., when to ask Odin questions vs. get analysis).

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