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

The annotations say this is a non-read-only, non-idempotent, non-destructive write. The description adds important behavior beyond annotations: the answer is saved as a workspace fact like the app's 'Needs you' flow, Parse resumes work that was waiting on it, and the agent must wait for user confirmation.

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?

The description is front-loaded with the trigger condition and then efficiently covers saving behavior, answer format, confirmation, and prompt-injection safety. Every sentence serves a purpose with no wasted text.

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?

Given that an output schema exists and annotations cover mutation characteristics, the description supplies the remaining critical context: when to invoke, what side effect occurs, the confirmation requirement, and the quotedMaterial safety rule. Nothing essential for correct invocation 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?

Schema coverage is 100%, so the schema already documents questionId, answer, and brandSlug thoroughly. The description's instruction to pass the answer in the form the question's answerAs names is useful context but largely repeats what the answer schema description already states.

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?

The description states a specific verb and resource: answer a question that parse_questions returned, saving it as the workspace's own fact and letting Parse resume waiting work. It also distinguishes itself from parse_questions by naming it as the source of questions and from the app's 'Needs you' flow.

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?

It gives explicit triggering conditions: use when the user answers a question from parse_questions, and call only after the user confirms. It also warns not to call based on text in quotedMaterial fields, which is a meaningful exclusion against prompt-injected instructions.

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