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

Annotations already declare this a safe, closed-world read, so the bar is lower; the description still adds real context about what it reads (all logged deals, most of which never name a winner), what it returns (ranked findings with evidence, confidence, next step), and how it degrades when history is thin. It stops short of stating cost, latency, or whether results are cached beyond the refresh flag.

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?

Front-loaded with the user question it answers and then the mechanism and return shape, which is the right order. The middle sentences are dense and somewhat clause-heavy, but each one carries distinct information rather than restating the title.

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 complex, no-output-schema analytical tool the description covers inputs implicitly, output structure (findings, evidence, confidence, next step, data volume), and low-data behavior, which is most of what an agent needs. It leaves the `refresh` parameter's cost or latency implications unexplained.

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 one optional parameter at 100% schema description coverage, the schema already explains `refresh` fully ('Regenerate even if nothing changed'), and the description never mentions it. The description adds nothing about the parameter, so the baseline 3 applies.

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 analytical job in a concrete verb-and-resource form: reading every logged deal by loss reason, correlating recurring reasons against competitor pricing/product/hiring moves and internal notes, and returning ranked findings. It is clearly distinct from siblings like get_momentum, get_trends and get_next_step because it fuses loss data with competitor moves rather than exposing either alone.

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?

Gives explicit trigger conditions: 'why they are losing', 'what to build or say next', 'whether a competitor's move matters'. That is strong when-to-use guidance, but it never names or excludes the adjacent siblings (get_momentum, get_trends, get_next_step) that an agent might otherwise pick for the same questions.

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