UpdateFunctionModule

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

Description mentions locks, update, unlock, optional activation, which adds behavior beyond schema. However, no annotations provided, and details like lock duration or failure handling are missing.

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?

Description is redundant (e.g., 'Operation: Update, Create. Subject: FunctionModule.' then 'Will be useful for updating or creating function module.'). Could be consolidated.

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?

No output schema or annotations. Description omits error conditions, return values, and detailed locking/activation behavior. Incomplete for a tool with 5 parameters.

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 covers all parameters with descriptions (100% coverage). Description adds no parameter-specific value beyond repeating schema info.

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?

Description claims both update and create, but input schema requires function_module_name to already exist, so create is misleading. Sibling including CreateFunctionModule further confuses. Purpose is not clear.

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 over alternatives like CreateFunctionModule or UpdateFunctionGroup. Lacks context for selection.

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