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

readOnlyHint=true already signals a safe, non-mutating operation, and the description adds that it produces compilable XML and should be followed by validation/write steps. It does not contradict annotations, but it also does not describe the exact return shape or failure 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?

Two sentences with no filler: the first states the purpose and accepted patterns, the second gives the required post-generation sequence. The critical constraints are front-loaded.

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?

For a 7-parameter tool with no output schema, the description gives the key workflow context (validate, then write) and the pattern domain. It could explicitly state the return type, but 'Generate...XML' and 'call validate_form_pattern on the result' make the output nature clear.

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%, so the heavy lifting is already done by the input schema. The description does not add parameter-level meaning beyond listing patterns, which is acceptable; it neither restates nor contradicts the schema.

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 ('Generate'), a concrete resource ('complete, compilable AxForm AOT XML'), and the key technical detail of correct control serialization. This clearly distinguishes it from sibling generators like generate_data_entity, generate_query, and create_aot_object.

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 explicitly enumerates the supported form patterns, telling the agent when the tool applies. It also prescribes a follow-up workflow: validate_form_pattern before write_aot_object. It lacks explicit 'do not use when...' alternatives, but the pattern list and pipeline are clear enough.

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