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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds beyond that: the empty-case behavior ("no results if the user has not created an idea yet") and the returned field set, which is meaningful since no output schema exists.

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-loaded with purpose, then usage, then return shape and edge case. The return-shape dump is somewhat verbose but earns its place since no output schema is present; no filler sentences.

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, describing the return object and the empty-result case is exactly the needed compensation, and the id-finding guidance rounds it out. The only gap is parameter documentation, which is not addressed anywhere.

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% and none of the three parameters (limit, offset, response_format) are explained in the description. The return shape mentions offset/has_more/next_offset, implicitly hinting at pagination, but the meaning of limit, offset bounds, and the markdown/json switch is left entirely undocumented.

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 (List) and resource (ideas) scoped to the signed-in user's workspace, and enumerates the returned fields (setup progress, run counts, signup counts, market read). This clearly distinguishes it from get_idea and the list_ad_runs/list_signups siblings.

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?

"Use this to find an idea id before calling any other idea tool" gives a concrete when-to-use condition, which is valuable given many siblings require an idea id. No explicit when-not or named alternative (e.g., get_idea) is provided, keeping it below a 5.

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