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

Annotations already declare readOnlyHint/idempotent/no-destructive, so the 'Read-only' sentence is largely redundant. What the description does add beyond structure is the scoping rule ('this user can answer' — not the whole brand's backlog) and the three answer modalities (choice / short text / email address), which directly shapes how the agent should prompt the user.

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?

Four short sentences, front-loaded with the trigger and ending with the follow-up action — no wasted clauses. The only near-waste is the standalone 'Read-only.' sentence, which just restates readOnlyHint=true already present in annotations.

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?

For a single-optional-param read tool with full annotation coverage and an output schema, the description covers the trigger, the scoping semantics, the answer types, and the correct next call. Nothing an agent needs to select and invoke it correctly is missing.

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?

Only one parameter and schema description coverage is 100%, with the schema itself explaining that omitting brandSlug uses the workspace's own brand. The description never mentions brandSlug, so it adds nothing over the schema — 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 — 'Returns the brand's open questions this user can answer' — and even gives the product-surface alias ('Needs you') plus the item shape. It stops short of naming the obvious siblings it is not (parse_get_question for a single question, parse_next_tasks for tasks), so an agent still has to infer the boundary.

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?

Opens with an explicit trigger ('when the user asks what Parse needs from them, or when a task waits on an answer') and closes with an explicit next step ('ask the user, then parse_answer_question'). No exclusion criteria are given, so it does not reach 5, but the when-to-use is concrete rather than implied.

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