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

Annotations already declare readOnlyHint and openWorldHint; the description adds meaningful behavioral context beyond annotations: the results are 'anonymous' and 'aggregated', the operation is 'free', and it requires the user to own the idea. No contradiction with annotations. Could be slightly more specific about what 'insights' include, but overall good transparency.

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?

Two sentences with no filler. The first sentence states the core action and result; the second provides usage guidance. Every word earns its place. Highly concise and front-loaded.

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?

Given that it has an output schema (covering return values), one parameter, and annotations that are well-aligned, the description is complete enough. It explains what the tool returns, when to use it, and the key precondition (owning the idea). No gaps.

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?

There is only one parameter (ideaId) with 100% schema coverage. The description adds critical extra meaning: 'pass an ideaId you own', which is not in the schema. This ownership constraint is essential for correct usage and goes beyond the minimal schema description.

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 uses a specific verb 'Return' and a clear resource 'cross-user intelligence for an idea', and explains it provides 'anonymous, aggregated insights from similar ideas across the platform'. This differentiates it from sibling tools like get_similar_startups or get_competitive_density by focusing on aggregated insights rather than specific startup matches.

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?

The description explicitly says 'Use it to learn how comparable ideas performed' and adds constraints: 'Read-only and free; pass an ideaId you own'. It provides solid context for when to use it but does not explicitly mention when not to use it or name alternatives like get_similar_startups, so it loses a point for lacking exclusion guidance.

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