create_new_function_api_v1_functions_create_post

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

With no annotations provided and a description lacking any behavioral details (e.g., idempotency, error handling, output description), the tool reveals no behavioral traits beyond the name.

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?

While the description is extremely concise (2 words), it provides no meaningful information. Conciseness should not come at the expense of utility.

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?

Given 4 required parameters with nested objects and an output schema, the description is wholly insufficient. It fails to explain what the tool does, how parameters relate, or the outcome.

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 0%, and the description adds no information about the 4 required parameters (id, name, content, meta). The nested meta object is completely undocumented.

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 New Function' is a tautology that restates the tool name without adding specificity. It fails to distinguish this tool from sibling creation tools like create_new_channel, create_new_chat, etc.

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 such as load_function_from_url or update_function_by_id. The description offers no context for decision-making.

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