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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral context on top: result ordering, the feature-flag prerequisite that causes empty results, and the conditional nature of the linked upload field ("once it has been turned into posts").

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?

Front-loads purpose and location, then returns, then next steps and prerequisite — logical order with no filler. The field enumeration in the second sentence is long but earns its place because there is no output schema.

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 enumerates the returned fields, discloses the feature-gating prerequisite, and points at the tools that consume the returned ids. An agent has everything needed to decide to call it and to use the result.

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 100% — limit (default 50, max 200), status enum values, and workspace_id sourcing from list_workspaces are all documented in the schema. The description adds no syntax or filtering nuance beyond that, so the baseline 3 applies.

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 and resource ("Lists content concepts (ideas/briefs)"), pins the location in the product UI (Library → Concepts), and specifies ordering (newest first). This clearly separates it from create_concept and update_concept in the sibling set.

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?

Explicitly names the follow-up paths ("Use the id with update_concept or create_post_drafts_from_concept") and states the prerequisite ("Requires Concepts to be turned on (Settings → Advanced)"). It stops short of an explicit when-not-use/exclusion statement, so it lands just below the top band.

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