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

Annotations already establish readOnlyHint=true, and the description adds useful security context: it reinforces that the tool must never receive raw credentials, API keys, account tokens, broker_config, bot_config, code, or env vars. It also clarifies the authenticated broker-connection dependency. It does not describe response format or pagination, but it adds meaningful context beyond annotations.

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?

The description is dense but front-loaded, starting with the read-only nature and broker connection scope before moving into parameter guidance. Every sentence carries operational meaning, though the single long final sentence is somewhat packed.

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?

Given 9 parameters, no output schema, and 0% schema description coverage, the description covers most calling conditions and security constraints well. It does not describe return values for the quote data, which is a gap, but it is complete enough to invoke correctly in most cases.

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 must compensate, and it does for most parameters: brokerCredentialId, symbols, quoteSymbol, assetType, expiration, strike, right, and exchange are all explained. The market parameter is not mentioned, and assetType enum values are only partially referenced, but overall the description adds substantial meaning beyond the bare 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 verb and resource: fetches current quote/last-price data from the signed-in user's saved broker connection. This distinguishes it from sibling tools like get_broker_option_chain and get_broker_account_snapshot by scoping to current quote data.

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?

Gives clear conditional guidance: pass brokerCredentialId or omit only when exactly one active broker connection exists; use symbols for one or more assets; use quoteSymbol only for crypto or forex; pass assetType option/future with the right supplemental fields. It lacks explicit naming of alternative tools, but the when/when-not conditions are strong.

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