Migration inventory of a legacy UI5 app

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

The description discloses the READ-ONLY behavior explicitly, which is a useful behavioral trait. However, no annotations are provided, so the description carries the full burden. It doesn't disclose what happens with invalid paths, whether concurrent calls are safe, or performance characteristics of scanning a large codebase. The READ-ONLY disclosure is valuable but the behavioral picture is incomplete.

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 a single dense run-on sentence that packs a lot of information. It front-loads the primary purpose and lists deliverables. It could be broken into shorter sentences for readability, but every phrase contributes meaningful context and there's minimal wasted text.

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 that the tool takes a single well-documented path parameter and has only one input, the description covers the essential scope well. However, there is no output schema and the tool returns a complex structured inventory (OData datasources, sections, bound fields, value helps, actions, OData calls), so the description could specify more about the return format, data shape, or any assumptions. For a complex output-producing tool with no output schema, the description could do more.

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% and there is only one parameter (appPath) with a clear description ('Legacy UI5 app root path'). The description reiterates what the schema says about appPath being the root path containing webapp/. The description adds the scope of analysis (manifest, XML views, controllers, i18n) which gives the parameter context, but since there's only one well-documented parameter, the baseline of 3 applies.

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 verb ('analyzes'), the resource (legacy freestyle UI5 app), the mode (READ-ONLY), and enumerates the specific inventory items returned (OData datasources, sections, tables, columns, bound fields, value helps, actions, OData calls). It distinguishes itself from siblings by focusing on analysis/inventory for migration, which is unique among the listed tools.

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 explicitly states when to use it: 'Use it as the starting point to migrate to modern CAP/Fiori.' It also names complementary tools to use alongside (cap_project_context and conventions://cap knowledge), providing clear guidance on sequencing within the migration workflow and distinguishing its role from related sibling tools.

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