form_generate_elements_runnable_item

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, and idempotentHint=false, so the safety profile is covered. The description adds nothing beyond the HTTP path, which merely restates the annotation title — no mention of side effects, whether generated elements are persisted, or what the item must contain.

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 short lines, front-loaded with the action. The appended endpoint path duplicates the annotation title and earns little place, but overall the definition is compact and not bloated.

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?

This is a mutation tool with a deeply nested body (FormSchemaFieldType, BindingAction references) and no output schema. The description says nothing about what elements are produced or how the body fields affect generation, leaving a substantial gap for an agent deciding whether and how to call it.

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% and the schema documents the nested body structure (id, type, name, bindings, parameters) plus externalType, so the description need not carry parameter detail. Baseline 3 applies; the description adds no meaning about how id/type drive element generation.

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 verb ('Generate') and a resource ('designer elements') scoped to a runnable item, so the general intent is inferable. But 'designer elements' is unexplained jargon, and the description offers no differentiation from close siblings such as form_generate_elements, form_generate, or form_generate_json_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?

There is no statement of when this tool should be used, what prerequisites (e.g. an existing runnable item with an id and type) are required, or how it differs from the many sibling form_* generation tools. The agent must infer everything from the name.

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