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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It conveys that the tool analyzes charts and returns technical signals, but it does not disclose whether the operation is read-only, what data source it uses, whether there are rate limits, or what the output format looks like.

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 concise sentence that front-loads the core action ('brutal chart analysis') before listing the included signals. It contains no filler or redundancy, though the word 'brutal' adds tone rather than substantive information.

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?

With one required parameter and no output schema or annotations, the description needs to explain what the address refers to and what kind of result to expect. It does neither, leaving an agent without the critical information needed to call the tool 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?

The schema has only one parameter, 'address', with 0% description coverage, and the tool description never mentions 'address' at all. The description does not help an agent determine whether the address should be a token contract, wallet, or pool, so it fails to compensate for the missing schema 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 identifies a specific action ('brutal chart analysis') and names concrete technical signals (RSI, MACD, support/resistance), making the tool's function reasonably clear. It is distinct enough from siblings like holder_analysis or token_price, though it never explicitly states what type of asset or address is being charted.

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 technical-signal phrasing implies the tool is meant for chart/technical analysis, but there is no explicit when-to-use guidance or mention of alternatives. An agent must infer the intended use case rather than being told when to choose this tool over a sibling.

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