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

Goes well beyond annotations by disclosing pagination limit and nextCursor, answerTotals and complete flag behavior, respondent identity rules (u_ vs e_), data preservation, consent non-grant, and untrusted-content warning. Rich operational context that annotations alone do not provide.

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?

Dense but front-loaded: primary purpose and action list lead, followed by pagination, identity, consent, and security details. No sentence is filler; each clause 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?

Given no output schema and annotations covering safety, the description supplies all needed operational, identity, consent, and pagination context to call the tool correctly across its four actions.

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?

Maps each action enum value to required parameters (cursor, surveyId, respondentId), adding substantial meaning beyond the generic payload schema which only lists example fields. The action-to-parameter mapping is precise and actionable.

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 'read' and resource 'surveys in the connected email workspace', enumerates the four sub-actions (surveyList, surveyGet, surveyResponses, surveyResponseHistory), making it instantly distinguishable from draft/publish survey 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?

Provides action-level context and a workflow guide link, but does not explicitly state when to choose this read tool over draft_email_survey or publish_email_survey, nor does it list exclusions. Usage is implied rather than guided.

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