UpdateFunctionModule

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

Discloses that the tool 'Locks, updates, unlocks, and optionally activates', which adds value beyond the schema. However, lacks details on lock type, permissions, side effects, or error handling.

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 short but includes redundant lines like 'Operation: Update, Create. Subject: FunctionModule.' and vague phrasing 'Will be useful for...'. The core operational sentence is clear but could be more streamlined.

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 5 parameters and no output schema, the description omits return values, error conditions, and post-update state. While it mentions activation, it lacks completeness for a robust understanding.

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 coverage is 100%, so baseline is 3. Description adds minimal extra context beyond schema (e.g., example in source_code), but does not significantly enhance parameter understanding.

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 'Update source code of an existing ABAP function module' and mentions locks, updates, unlocks, and activate. However, it ambiguously includes 'Create' which contradicts the schema requirement that the function module must already exist, and a sibling CreateFunctionModule exists.

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 explicit guidance on when to use this tool versus alternatives like CreateFunctionModule or ActivateFunctionModule. No exclusions or prerequisites mentioned beyond schema.

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