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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing cost ($2 USDC per call, x402), the billing safeguard ('If too few sources answer you are not charged'), and the async nuance that with async=true the core source is checked before the job is queued and charged. It also describes the output shape (model-written quality score, bull/bear cases, PDF link) — exactly the kind of operational context the annotations cannot carry.

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 deliverable and its sources, then immediately covers the two things an agent must know before calling — cost and billing behavior. The source enumeration sentence is dense, but every clause maps to real output content rather than filler.

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 carries the return-value burden and does so: report contents, PDF, quality score with bull/bear cases, and the job-id/async path. Only the webhook delivery behavior is left unexplained, which is a minor gap for a tool that is otherwise thoroughly specified.

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 75%, so the baseline is 3, but the description adds real semantic value on 'async' by explaining the pre-queue source check and the charge/no-charge consequences, which the schema only glosses as 'Return a job id now and the report later.' 'pdf' is corroborated ('a PDF') but 'webhook_url' is left entirely to 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 deliverable (an equity brief for any US-listed company) and enumerates the exact primary sources it draws on (SEC fundamentals, Form 4 insider activity, 8-K events, news, macro). It is clearly distinguishable from price/quote tools by the explicit 'No live prices' scope. It never names or contrasts with the nearby report_company sibling, so it falls short of explicit sibling differentiation.

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?

Usage is implied rather than stated: 'Equity brief ... from primary sources' plus 'No live prices' tells the agent this is fundamental research, not a quote. However, no when-to-use condition or named alternative (e.g. report_company, insider, sec_events, report_market) is offered, leaving the agent to infer routing among a very crowded reporting family.

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