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

Annotations already establish the read-only, idempotent, non-destructive profile, so the description's added value is the ownership scoping rule ('returns an error if the idea id does not belong to the signed-in user') and the readiness/fix behavior. That is genuine context beyond the annotations, though rate limits and pagination are unaddressed.

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?

Three tightly-packed sentences: purpose first, then usage context, then return shape and the error case. No filler, everything is front-loaded and earns its place.

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 steps in by sketching the return object (idea, readiness, readyToLaunch, activeRuns, recentRuns) and the error condition, which is nearly enough to call it confidently. The unaddressed response_format parameter is the one remaining gap.

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 0% for two parameters. The description only implicitly identifies ideaId as an idea identifier owned by the user; response_format (markdown vs json) is never mentioned, so the description does not compensate for the undocumented schema.

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?

States a specific verb+resource ('Get one idea in detail') and enumerates exactly what the detail contains: setup progress, readiness checklist, active runs, recent runs. This clearly distinguishes it from siblings like list_ideas and get_ad_run.

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?

Gives an explicit usage context ('Use this to answer "is this idea ready to test?"'), which tells the agent when to reach for it. It does not name alternatives or exclusions, so it falls short of a 5.

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