get_functions_api_v1_functions_export_get

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It merely states 'Get Functions' with no mention of read-only nature, authentication requirements, export behavior, or the effect of the 'include_valves' parameter.

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 extremely concise at two words, the description is under-specified and fails to communicate essential information. Brevity here sacrifices clarity.

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 the presence of many sibling function tools and the existence of an output schema, the description is severely incomplete. It does not clarify the output format, the meaning of 'export', or how this tool fits into the broader set of function operations.

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%, meaning the parameter 'include_valves' has no description in the schema. The description does not compensate by explaining what this parameter does, leaving the agent without guidance on its purpose.

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 is 'Get Functions', which is a tautology of the tool name. It does not specify that this tool is for exporting functions (as the name 'export_get' suggests), nor does it distinguish from siblings like 'get_function_list_api_v1_functions_list_get' or 'get_functions_api_v1_functions'.

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 other function-related tools such as listing, retrieving by ID, or exporting in different formats. The description lacks any usage context.

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