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

The readOnlyHint annotation already covers the safety profile, and the description does not contradict it. The description adds cost/plan context but does not disclose behavioral details such as ordering direction, pagination behavior, or response shape. Since annotations carry the main burden, this is adequate but not rich.

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 core purpose is front-loaded in the first sentence, and the pricing/plan information is condensed into the second. It is concise and readable, though the 'Understanding plan.' fragment is slightly abrupt.

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 convey what the agent will receive, and it does indicate a ranking by signal count. However, it omits return field details, sort direction, and pagination defaults beyond schema defaults, leaving moderate gaps for a simple listing tool.

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 only 33%: only `context` has a description, while `page` and `limit` rely on type/default constraints. The tool description adds no parameter-level guidance and does not compensate for the low coverage, even though the parameter names are conventional.

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 clearly states a specific verb and resource: a 'cross-section ranking' of '40 tracked investment dimensions' by signal count. It distinguishes itself from the more general insights_overview and insights_industries by focusing on dimensions, but it does not explicitly name or contrast any sibling tool.

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 guidance on when to use this tool versus alternatives like insights_adoption, insights_industries, or find_company_insights. The pricing and plan information is useful operationally, but it does not help an agent decide between this and sibling tools.

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