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

Annotations already declare the safety profile (readOnlyHint, destructiveHint=false), so the bar is lower, and the description adds substantial value by enumerating the return contents (fields, optionScores, optionParts, showWhen, scoring, calculator/delivery settings, updatedAt). It also discloses the optimistic-concurrency role of updatedAt, though it does not spell out authorization or error behavior.

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 purpose is front-loaded in the first sentence, followed by the return inventory and the workflow instruction. The dense return list is informative rather than padded, though it could be tightened.

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?

With no output schema, the description carries the return-value burden and does so thoroughly, and the two required params are covered by the schema. Combined with annotations covering safety, an agent has enough to call it correctly, with only minor gaps in error/edge-case behavior.

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 description coverage is 100% for both formId and projectId, so the schema already documents the parameters fully. The description adds no syntax or format detail beyond the schema, so the baseline 3 is appropriate.

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 ('Get one form') and scopes it precisely ('its complete schema'), which cleanly separates it from list_forms and get_form_submissions. An agent can identify this as the single-form read tool without opening the schema.

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 tells the agent to 'Read here before update_form_schema' and to pass the returned updatedAt as expectedUpdatedAt, naming the sibling and the sequencing rule. This is actionable when-to-use guidance rather than vague context.

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