vibo_answer_question

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

Annotations (readOnlyHint=false) indicate write; description confirms write. Adds confirm-gated preview behavior and local path requirement for files. Does not cover error scenarios or success output, but overall adds value beyond annotations.

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 sentences, no fluff. First sentence defines purpose, second sentence lists field mappings. All content earns its place.

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?

Complete for a 10-parameter, 3-required tool with no output schema. Covers all parameter usage contexts, confirm gate, and references sibling tool for IDs. No missing guidance.

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%, but description adds crucial context: fields are mutually exclusive per question type, referenced vibo_list_section_questions for IDs, and explain confirm as gatekeeper. This significantly enriches schema descriptions.

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 clearly states 'Answer a section planning question' with a specific verb and resource. It distinguishes from sibling tools: no other sibling answers questions (vibo_list_section_questions lists them).

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 maps question types to fields: text for text, selectedOptions for radio/checkbox/select, link for link, imagePaths/filePaths for photo/file. Includes confirm-gated behavior and otherOptionTitle usage.

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