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

The annotations already indicate this is a write operation (readOnlyHint=false). The description adds behavioral context beyond annotations by explaining draft vs. published status and the consequence of 'immediate portal access' when published. It is consistent with the annotations and adds useful nuance.

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 two short sentences, immediately starts with the action and resource, and contains no filler. Every phrase contributes meaning, making it highly efficient.

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 the tool has 9 parameters including nested objects (questionBlocks, settings) and there is an output schema, the description is brief. It covers creation and publishing but does not clarify the structure of the required questionBlocks array, leaving the agent to rely entirely on the schema and output schema for structural details.

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?

All 9 parameters have schema descriptions (100% coverage), so the baseline is 3. The description echoes some parameter meanings ('custom question blocks' for questionBlocks, 'set status to published' for status), but it does not add extra format or syntax details beyond what the schema already provides.

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 'Create a survey' with a specific resource and adds scope via 'custom question blocks.' It also mentions the publish behavior, which provides useful context, but it does not explicitly differentiate from closely related siblings like update_survey.

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?

The description implies when to use the tool (when creating a survey) and gives a functional hint about publishing ('Publish it later or set status to published'). However, it does not state when not to use it or name alternatives such as update_survey or create_survey_invitation.

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