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

No annotations exist, so description carries full burden. It only states 'single-call convenience endpoint' implying aggregation but does not disclose side effects (likely read-only), rate limits, or data recency. Minimal behavioral disclosure.

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?

Two concise sentences front-load the purpose and composition of the payload. No wasted words; every sentence earns its place.

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 no output schema, description should clarify return value structure. It mentions components but lacks details on format, fields, or what 'indices' refers to. Context is adequate for a simple aggregation tool but incomplete for precise agent 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?

Tool has zero parameters and 100% schema coverage. Description need not add parameter details; baseline of 4 is appropriate. It does not explain output structure, but parameter semantics dimension is satisfied.

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?

Description clearly states the tool provides a complete signal payload combining phase_signal, ji_sensing, and indices, and identifies it as a convenience endpoint. This distinguishes it from sibling tools like phase-signal or ji-sensing, but the verb is implicit (assumed to be 'retrieve' or 'get'), not explicit.

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 vs. sibling tools (e.g., 'use this instead of calling individual endpoints'). No explicit context about preferred scenarios or when not to use it.

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