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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context by noting that results carry a security_id and that multiple share classes may appear for one name. It says nothing about result volume, pagination, or how broad name matching behaves.

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 with no filler, and the core action is front-loaded before the follow-on advice. Slightly more could be earned by folding in the pagination or empty-query behavior rather than leaving the second sentence purely about downstream use.

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?

An output schema exists, so return-value explanation is not required, and the description correctly points at security_id as the key field. The gap is on the input side: with three undocumented, all-optional parameters and a default empty query, an agent lacks enough to know how to page or how to trigger a full listing.

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 carry parameter meaning. It clarifies that the query accepts either a symbol or a name, which is real added value, but limit and offset are left completely undefined — an agent cannot tell whether limit defaults to a page size or a cap, nor how offset interacts with the default empty query.

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 uses a specific verb and resource ("Find registered securities") and names the two lookup keys (symbol or name), which clearly distinguishes it from the task/report-oriented siblings. It stops short of explicitly naming a sibling as the alternative path, but the purpose 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?

The second sentence gives a downstream usage hint — use the returned security_id to disambiguate share classes — which implies this is a lookup step preceding other calls. However, there is no explicit when-to-use versus when-not-to-use guidance, no mention of what an empty query does, and no stated prerequisite for calling it.

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