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

Adds substantial context beyond the readOnlyHint/openWorldHint annotations: explicit content exclusions ('carries NO quantity and NO instruction', sizing reads 'not provided'), a disclaimer that it is not advice or a prediction, the transport (GET URL), per-call cost (0.005 credits), and an unauthenticated rate limit (25 calls/day per address). This is exactly the kind of operational detail annotations cannot supply.

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-loads what the tool produces and its exclusions, then tucks endpoint/cost/auth facts into a parenthetical. Every sentence carries information, though the parenthetical is dense.

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 sketches the returned content, but it omits any explanation of the `guru` and `quarter` inputs, including valid formats or the default period. For a 3-parameter tool at 0% schema coverage, that leaves a real gap an agent must guess at.

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 0% and the description only surfaces `ticker` via the URL template. The required `guru` parameter and the optional `quarter` (a date-formatted field with obvious ambiguity about which quarter) are left completely undefined, so the description does not compensate for the coverage gap.

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 output artifact (a flattened brief of one filed move) and enumerates exactly what it contains (what the investor did, when, price, value band, verdict sentence). It explicitly distinguishes itself from the sibling `verdict` by describing the relationship ('the same move as /verdict, flattened').

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 comparison to /verdict implies this is the lighter-weight alternative that omits sizing, but it never states when to choose one over the other or any preconditions for calling it. Usage is inferable rather than explicit.

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