Get daily prices

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds the result-cap context ('Max 20 per page'), though that duplicates the pageSize maximum of 20 in the schema, and it does not say what happens when fromDate is omitted or whether pagination continues until exhausted.

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?

Two compact sentences with the payload contents front-loaded and no filler. It is efficient, though the terseness leaves behavioral gaps that other dimensions penalize.

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 six-parameter read tool with full schema coverage and no output schema, the definition covers what the rows contain but omits pagination traversal guidance and date-range defaults (notably the absence of a stated default for fromDate). Adequate as a minimum-viable definition, not complete.

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 every parameter including issuerId's provenance and the pageSize bounds is already documented. The description's only parameter-adjacent statement restates the 20-per-page cap, adding no meaning beyond the structured fields.

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?

Names the specific resource (daily prices) and enumerates the returned measures (OHLC, volume, NAV, application/redemption) for a single security, which separates it from siblings like get_top_holders or list_distributions. The retrieval verb is only implied by the name, but the content scope is unambiguous.

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?

No guidance on when to use this versus other data tools, no mention that issuerId must be resolved via list_issuers, and no statement about required date-range behavior. The agent must infer all invocation context from the schema alone.

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