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

Annotations already establish this is a safe, read-only, closed-world operation, but the description adds substantial context: the full field composition of each idea (problem, feature, MVP, effort, backer count, posts, key), the meaning of 'kind missing' vs 'unsaid', the exclusion of done/skipped ideas, and that run status, next-free slot, and current price are also reported. This goes well beyond the annotation hints.

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 description is a single dense paragraph that crams return-field definitions, taxonomy explanations, filtering rules, and pricing into one run-on structure with minimal front-loading. The definitions of 'kind missing' and 'unsaid' are buried mid-sentence, and the trailing 'Free.' is disjointed, making it hard to scan.

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 and no parameters, the description carries the burden of describing returns, and it does enumerate the fields each idea contains plus the ancillary run/price info. It is fairly complete for a zero-arg read tool, though the structure makes it harder to extract than it should be.

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?

The tool takes zero parameters and the schema is empty, so there is nothing to document. Baseline 4 applies; the description correctly does not fabricate parameter detail.

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 identifies the resource: the latest feature-ideas study aggregating what Reddit and X users ask for, grouped into features. An agent can tell this is a retrieval of feature ideas. However, it never explicitly differentiates itself from close siblings like build_ideas, ideas_run, or ideas_skip beyond noting that done/skipped items are excluded.

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 explains what is filtered out (ideas done via meta.idea or ideas_skip) but never states when to call this versus ideas_run, build_ideas, or other siblings. There is no 'use this when' guidance and no prerequisites, leaving the agent to infer the selection context entirely.

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