form_generate

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds two genuinely useful facts not in the annotations: the tool is deprecated, and the result is a ProviderSchemaImpl suitable for custom resource type creation. It does not disclose auth requirements, whether the generated schema is persisted, or the response shape.

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 deprecation warning is correctly front-loaded and the whole definition is four short lines. There is mild redundancy: 'Generate schema for runnable item' and 'Generate a ProviderSchemaImpl for the provided RunnableItem' say substantially the same thing, and the trailing POST path merely repeats the annotation title.

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 schema-generation tool with a deeply nested body and no output schema, the description does explain what comes back (a ProviderSchemaImpl usable to create a custom resource type). What is missing is the deprecation follow-up — what to use instead — and any differentiation from the several similarly named generate siblings, which is the biggest practical gap for an agent.

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 single body parameter carries a 'Runnable item' description plus nested field documentation for inputBindings, inputParameters and outputParameters. The description adds no parameter-level meaning beyond restating that a RunnableItem is provided, so this sits at the baseline where the schema does the work.

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 artifact: it generates a ProviderSchemaImpl from a supplied RunnableItem, which can then be used to create a custom resource type. The deprecation marker and the underlying endpoint add concreteness. However, it never distinguishes itself from close siblings such as form_generate_elements_runnable_item, form_generate_json_schema, or form_generate_elements, so an agent cannot route between them from this text alone.

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 explicit when-to-use statement, no when-not-to-use, and no named replacement for a tool flagged DEPRECATED. The phrase 'can be used to create a custom resource type' describes downstream purpose rather than invocation conditions. An agent is left to guess whether to call this or one of the other schema-generation siblings.

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