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

Annotations already declare readOnlyHint=true, so the description's 'Read-only and free' adds no new transparency there. However, it adds value by noting the idea must be 'already validated' and owned, and by explaining the tool's internal approach (combining corpus benchmarking with VC scoring). No contradictions with annotations.

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 two sentences: the first states purpose and output, the second tells when to use and constraints. Every word earns its place with no redundancy. Front-loaded with key value proposition.

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?

The tool has an output schema (not shown but noted present), so the description doesn't need to explain return values. It covers purpose, usage context (validated owned ideas), and safety (read-only, free). With 2 simple params and full schema coverage, this is complete.

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 coverage is 100%, so baseline is 3. The description adds value by implying that ideaId must refer to a validated, owned idea, which goes beyond the schema's bare 'The idea ID'. It also implies language is a response format choice, aligning with the enum. This extra context justifies a 4.

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 the tool returns 'AI-powered improvement suggestions for an idea' that combine 'corpus benchmarking with VC scoring insights into concrete next steps'. The verb 'Return' and resource 'improvement suggestions' are specific, and 'concrete next steps' distinguishes it from other get_* tools like get_validation_snapshots or get_expert_feedback.

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 says when to use it: to 'understand exactly what would raise an idea score'. It also provides context: 'pass an ideaId you own that has already been validated'. However, it doesn't explicitly exclude alternatives or mention when NOT to use it compared to siblings like get_pivot_suggestions.

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