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

With readOnlyHint/idempotentHint already declaring the safe-read profile, the description adds the non-obvious dual-mode behavior: no arguments returns the overview, while passing an id from a previous result opens that group. It stops short of describing result size, pagination behavior, or what the 'people under each' entries contain.

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?

Front-loaded purpose sentence, then usage triggers, then mechanics, then the sibling handoff — a logical order with no filler. The parenthetical example queries add value but make the middle sentence slightly long.

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?

Covers purpose, triggers, drill-down mechanics and routing, which is most of what a zero-required-param read tool needs, and no output schema exists so return shape needn't be explained. The missing piece is pagination behavior, which matters given a 60-item cap.

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 0%, so the description must carry parameter meaning. It does explain that company_id, role_id and industry_id come from a previous result and open that group, but says nothing about limit and offset (defaults 20/0, max 60), leaving two of five parameters entirely undocumented.

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: shows companies, roles and industries where the user can get a warm introduction, with the people under each. It is clearly distinguished from search_members (named company/role lookup) and from the networking-outreach siblings.

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 explicit triggers with quoted example user intents ('which banks can I get an introduction at', 'what tech companies could I network into'), explains the no-argument overview mode, and names the alternative to use for a named company or role. When-to-use and when-not-to-use are both covered.

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