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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds useful payload context — that results include each firm's quoted sentence and the source page — which stands in for a missing output schema, but it says nothing about cardinality, pagination, or behavior on an unknown key.

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?

One meandering sentence that opens mid-thought with 'Every firm that says...' rather than leading with the action or resource. It is short in absolute terms but is hard to parse and front-loads subordinate clauses instead of the core purpose.

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 one-parameter read tool with no output schema, the description does convey what the returned data contains, which is the main gap it needs to fill. However, an agent still lacks explicit confirmation of what the tool returns structurally and how it relates to list_affiliations or get_firm.

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 coverage is 100% and the single 'key' parameter is fully documented with its accepted forms (group key or corridome.com address). The description adds no additional meaning beyond that, which is the expected baseline when the schema does the work.

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 sentence describes the resource's contents (firms claiming a broker-dealer/network/franchise affiliation, with the site sentence and page) but never states a verb for what the tool does. It is inferable as a lookup of one affiliation group, but it does not cleanly distinguish this from siblings like list_affiliations or get_firm without effort.

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 when-to-use guidance, no mention of how this differs from list_affiliations, and no statement of prerequisites. The only routing hint ('key from list_affiliations') lives in the schema, not the description.

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