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

With no annotations, the description carries the burden of disclosing behavior. It reveals the core output (ranking by signal count) and the fixed dimension set, but it omits details like output format, default sorting, pagination behavior, or what constitutes a 'signal'. The behavior is simple and read-only in nature, so 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 main sentence is concise and front-loaded with the core behavior. However, the trailing fragment 'Understanding plan.' does little to earn its place and adds ambiguity rather than clarity. It is efficient overall but imperfectly structured.

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 simple ranking tool with no output schema and no annotations, the description gives the essential idea but leaves notable gaps: no mention of pagination defaults, no clarification of 'signal', and no relation to other insight tools. An agent could call it, but might miss pagination or expected output nuances.

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), and the description adds no parameter information. Page and limit have no explanations and the description does not compensate for the low coverage. The context parameter's purpose is well-explained in the schema, but the description itself adds no semantic value for parameters.

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 states a specific resource (40 tracked investment dimensions) and a specific operation (cross-section ranking by how many profiled companies show signal). This clearly distinguishes it from siblings like insights_adoption or cohort_rankings, though it does not explicitly name a sibling alternative.

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. It does not state what scenario fits this ranking, how to decide between this and insights_adoption or other insights tools, or any exclusions.

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