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

Annotations already declare readOnlyHint=true and idempotentHint=true, so safety and repeatability are covered without description effort. The description adds domain context (these securities drive fill pricing) but says nothing about auth requirements despite an apiKey parameter, nor about result size or pagination.

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 short sentences, no filler, with the resource and its content front-loaded and the significance statement following. Every clause carries information.

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, listing the returned fields is a genuinely useful substitute, but the definition is silent on the required 'instance' parameter's meaning and the apiKey argument, leaving an agent without enough to invoke it confidently in an unusual context. Adequate for a simple read, but with clear gaps.

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%, so the description carries the full burden for the two parameters, yet it never explains what 'instance' must be or what apiKey is for. The only indirect hint is the phrase 'configured on an instance', which gestures at the required parameter without clarifying its format or scope.

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?

The description names the resource (securities) and enumerates its contents (symbol, last price, CUSIP, ISIN) plus the scoping context ('configured on an instance'), which clearly separates it from sibling list tools like list_orders or list_executions. It never states the verb explicitly, but the 'list' semantics are unambiguous from the name and content.

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?

There is no statement of when to call this versus alternatives, no prerequisites, and no exclusions. The clause 'FIXSIM prices fills from these' hints at why the data matters (related to fills), but it is not actionable routing guidance.

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