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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuine context by disclosing the returned content categories and flagging that net worth is an estimate and performance is a score, which tells the agent the data is derived rather than raw. It stops short of saying anything about freshness, provenance, or cost.

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?

A single front-loaded sentence with zero filler; the resource and its contents are stated first and nothing is repeated from the title or schema.

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, the description must describe the return payload, and it does so by listing the four content categories. For a one-parameter read-only lookup with annotations, that is close to sufficient; only the link back to search_insiders is missing.

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?

Only one parameter and schema description coverage is 100%, so the schema already carries the full burden; the schema text itself ('Insider id') is tautological and the description adds nothing about id origin or where to obtain it. Baseline 3 applies when structured fields do all 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?

States a specific verb (Get) and resource (insider's enriched profile) and enumerates the payload: biography, roles, net worth estimate, trading-performance scoring. That is markedly more informative than a bare 'get profile'. It never distinguishes itself from the sibling search_insiders, which is the main gap keeping it below a 5.

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?

Usage is only implied: the required insider_id signals a detail lookup that follows an insider search, but the description never says when to reach for this instead of search_insiders or any other sibling. No prerequisites, no exclusions, no alternatives named.

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