strategy

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

Annotations declare readOnlyHint=true, but the description adds little beyond that. The phrase 'long-term insight' hints at non-destructive behavior, but no details on what the tool does internally or what outputs to expect.

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 sentence that largely restates the tool name ('Investment strategy'). It is under-specified rather than concise, lacking critical information about the tool's functionality.

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?

Despite having an output schema (not provided), no details on return values are given. With many sibling tools, the description fails to explain what makes 'strategy' distinct or what it produces, leaving the agent without sufficient context to invoke it correctly.

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% (zero parameters). Baseline is 3 since description provides no additional parameter semantics; there are no parameters to document.

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 'Investment strategy: target_assets + Dreaming long-term insight' is vague and only loosely defines the tool's purpose. It does not specify a clear action (e.g., 'retrieve', 'compute') or resource, and does not differentiate from sibling tools like 'decisions' or 'what_if'.

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. With 18 sibling tools covering actions like 'buy', 'sell', 'decisions', the description should indicate the appropriate context for 'strategy'.

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