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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description's help. The description's real addition is the reference format for downstream use (about: [{kind: "idea", id}]), which tells the agent how an idea id composes into other calls. It says nothing about result volume, ordering, or whether "open" excludes already-written or dismissed ideas.

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 short sentences, roughly 20 words, with the resource statement front-loaded and the chaining instruction second. Nothing is padded. Minor deduction because the parenthetical field list reads as a fragment and the whole thing borders on under-specified rather than tight.

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 one optional parameter, no output schema, and full annotation coverage, the definition is workable but leaves real questions open: how many ideas come back, whether there is pagination, and what "open" excludes in practice. For a discovery/list tool that seeds a write workflow, those are the details an agent most needs before deciding whether to call it or uptake_more_ideas first.

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 single parameter `project` has 100% schema description coverage including the id-or-site format and the single-project fallback, so the schema does the work. The description never mentions `project` and adds no scoping semantics of its own. Baseline 3 applies when schema coverage is high and the description neither compensates nor misleads.

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?

"Open post ideas" names the resource and the filtered scope (open), and the parenthetical enumerates the fields an idea carries (title, angle, network), so the agent knows what it is getting back. It also identifies uptake_write_post as the follow-up action that consumes an idea id. It stops short of an explicit verb or distinguishing itself from near-siblings like uptake_more_ideas and uptake_dismiss_idea, which also act on ideas.

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 second sentence gives a concrete next step ("Write one with uptake_write_post, about: [{kind: "idea", id}]"), which is genuinely actionable chaining guidance. However, there is no statement of when to call this versus uptake_more_ideas (generate ideas) or uptake_dismiss_idea (discard one), so the routing decision among idea-related siblings is implied rather than specified.

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