ht_dcphase

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

No annotations are provided, and the description offers no behavioral information. It doesn't disclose whether this is a read-only operation, what data sources it uses, potential rate limits, error conditions, or any other behavioral traits needed for reliable invocation.

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 extremely concise with just 5 words, front-loading the core purpose without any unnecessary elaboration. Every word serves a functional purpose in identifying what the tool does.

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 tool with 4 parameters (2 required), no annotations, no output schema, and 0% schema description coverage, the description is completely inadequate. It provides only basic purpose identification without any of the contextual information needed for proper tool selection and invocation.

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?

With 0% schema description coverage for all 4 parameters, the description provides no information about what 'symbol', 'interval', 'month', or 'datatype' mean, their expected formats, or valid values. The description doesn't compensate for this complete lack of parameter documentation.

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 states the tool fetches the Hilbert transform dominant cycle phase, which is a specific technical indicator. However, it doesn't explain what this indicator measures or how it differs from similar sibling tools like ht_dcperiod, ht_phasor, or ht_sine, leaving the purpose somewhat vague for non-experts.

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 is provided on when to use this tool versus alternatives. The description doesn't mention any context, prerequisites, or comparisons to sibling tools, making it impossible for an agent to determine appropriate usage scenarios.

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