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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds the classification inputs and a detailed return-field list, but says nothing about fetch latency, auth, or rate limits when candles are omitted and venue retrieval is required.

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?

A single dense paragraph that is front-loaded with the purpose, then the method, then the use-case trigger, then the returns. It is longer than minimal but every clause carries information; minor tightening of the classification label list would help.

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 no output schema, the description usefully enumerates the returned fields (structure, bias, key_signals, key_levels, tails, scenario_framing, invalidation), which is exactly the compensation needed. It remains silent on error/fallback behavior when venue fetching fails, but is otherwise sufficient for a read-only classifier.

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 description coverage is 100%, so all seven parameters (including enums for venue and timeframe) are already documented, making 3 the baseline. The description's mention of TPO/initial balance/value migration hints at what drives the computation but adds no syntax or value guidance beyond the schema.

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?

States a specific verb+resource: a Market Profile day-type classifier producing trend/balance/neutral_trend/normal/normal_var. It names the exact feature set (TPO, initial balance, range extension, value migration) and the sibling namespace is large, yet this is clearly the only day-type classifier.

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?

Provides a concrete context trigger: 'Use for "is this a trend day or a balance day?"'. That maps the tool to a recognizable analytic question, but it names no exclusions or alternatives even though sibling tools like run_value_migration and run_breakout_acceptance overlap in the profile/auction space.

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