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

Beyond the readOnlyHint annotation it discloses the genuinely decision-relevant behaviors: no new model call is triggered (latency/cost), a 404 is returned when no current read exists, and one read is charged against the monthly allowance once per ticker per day. That quota-and-caching detail is exactly the kind of thing an agent must know before calling, and it is not derivable from annotations or schema.

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?

Three tight sentences: what it returns first, then cost/side-effect semantics, then quota accounting. No filler, and the most decision-relevant constraints are front-loaded.

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 an output schema present it need not describe return shape, and the readOnly annotation covers the safety profile. What remains — cost, caching, 404 conditions, quota consumption — is all stated, making the definition sufficient for correct invocation.

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?

There is a single required parameter, `symbol`, with 0% schema description coverage, so the description would need to compensate by specifying ticker format or exchange conventions — it does not. The parameter is conventional enough that an agent can plausibly guess, but the definition leaves format ambiguity unresolved.

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?

It names a specific resource — the ticker's current AI analyst read — and enumerates its contents (lean, conviction, thesis, six fixed sections, evidence for/against, invalidation condition), so the agent knows exactly what payload to expect. It references sibling `rayana_ai_analyst_read` only obliquely (it 'also reports what remains'), leaving the precise scope difference between the two tools partly inferred rather than stated.

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 only implied: fetch this when you want the AI read for a given ticker. There is no explicit when-to-use versus siblings like `rayana_ai_ticker`, `rayana_ai_analyst_brief`, or `rayana_ai_analyst_read`, and no stated preconditions (e.g., subscription tier) beyond the quota note.

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