Generate a Fiori elements app for an OData service (non-CAP)

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

Annotations only state non-read-only, non-idempotent, non-destructive. The description adds concrete behavioral detail by listing the files it generates (manifest.json, Component.js, etc.), which tells the agent what side effects to expect. It does not mention overwrite behavior or permissions, but the annotations already cover the safety profile.

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 three sentences with the main purpose front-loaded, followed by input guidance and output artifacts. The floorplan enumeration partly duplicates schema enum descriptions, but the summary is compact and each sentence carries meaningful information.

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?

An output schema exists, so return details need not be explained. The description covers the high-level workflow and references a sibling tool, but it does not clarify parameter groups (e.g., serviceUrl vs systemName vs destination/servicePath) and contains the misleading 'metadataXml content' reference. Given 15 parameters, the description is adequate but leaves some gaps filled only by the schema.

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 100%, so the baseline is 3. The description adds a useful rule about alternative metadata inputs, but it references 'metadataXml content' which is not a parameter in the schema, misleading the agent. The 'or just entitySet' hint is helpful, but the inaccurate reference outweighs that benefit.

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 states a specific verb ('Generates') and resource ('SAP Fiori elements application') with an explicit scope ('OData V2/V4 service... non-CAP'). It distinguishes from the obvious sibling generate_fiori_app_cap via the parenthetical and clearly enumerates the output artifacts, leaving no ambiguity about what the tool does.

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?

The description signals when to use this tool by the 'non-CAP' qualifier, implying CAP projects belong to generate_fiori_app_cap. It also gives workflow guidance by referencing download_odata_service_metadata as the source for metadataXmlPath and hints at fallback input modes ('or just entitySet'). However, it does not explicitly name alternatives like create_ui5_app or state when to avoid this tool.

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