call_function

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

No annotations exist, so the description bears full responsibility. It only states 'call a stored function with positional params' without disclosing behavioral traits such as side effects, authorization requirements, error handling, or whether the function is read-only or modifies state. This is critically insufficient.

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 one sentence, concise and front-loaded with the core action. However, it sacrifices completeness for brevity. For a simple tool, this level of conciseness is acceptable but not ideal when compared to richer alternatives.

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 absence of an output schema and annotations, the description fails to explain return values or behavior. The tool has 4 parameters (1 required) and moderate complexity, but the description offers no context on outcomes or integration with other tools. It is far from complete.

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?

With 50% schema description coverage, the description should compensate for undocumented parameters. However, it adds no extra meaning; it merely mentions 'positional params' without elaborating on the 'params' array structure or the 'function' name. The information provided repeats what the schema already conveys for 'database' and 'connection'.

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 clearly states the tool calls a stored function with positional params, but lacks differentiation from the sibling 'call_procedure'. The verb 'call' and resource 'stored function' are specific, but the brevity leaves ambiguity about what distinguishes a function from a procedure.

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 on when to use this tool versus alternatives like 'call_procedure' or other execution tools. No context about prerequisites, limitations, or typical use cases is provided.

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