create_udf

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

No annotations are provided, and the description does not disclose any behavioral traits such as idempotency, validation, or side effects. For a creation tool, the agent needs to know if it can overwrite existing UDFs or what happens on duplicate, but none is mentioned.

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 a single short sentence, which is concise. However, it is too sparse for a tool with a complex parameter like 'udf_config', and the lack of structure (e.g., sections) makes it difficult to scan.

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?

Despite having an output schema and a single parameter, the description provides almost no context. The agent would not understand what the UDF is, what inputs it accepts, or what the output contains. The tool is incomplete for effective use.

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?

The input schema has 0% description coverage, and the description does not mention the 'udf_config' parameter or explain its expected structure. The 'additionalProperties: true' suggests a flexible schema, but the agent gets no guidance on required fields or format.

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 'Create custom UDF.' clearly states the action (create) and resource (custom UDF), distinguishing it from siblings like 'list_udfs', 'get_udf', 'update_udf', and 'run_udf'. However, it does not explain what a UDF is or what 'custom' implies, leaving some ambiguity.

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?

No guidance is provided on when to use this tool versus alternatives like 'run_udf' or 'update_udf'. The context signals show many related tools, but the description lacks any cues about prerequisites or scenarios.

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