Summarize a metadata.xml

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the local-file input context and the summary output items, but it does not discuss failure behavior for invalid XML or missing files. This is adequate but not strongly additive beyond the annotations and output schema.

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 with no filler. It front-loads the key scoping term 'local' and the result list, and every word contributes to understanding what the tool does.

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?

For a single-parameter, read-only tool with a rich output schema and safety annotations, the description is complete enough for correct invocation. It specifies the local file input and summarizes what will be returned; no additional context is needed.

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%: the single parameter metadataXmlPath is already documented as 'Path to the metadata.xml file'. The tool description adds no additional parameter semantics such as absolute/relative path requirements or file format constraints, so the baseline 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 states a specific verb ('parses'), a specific resource ('local EDMX metadata.xml'), and enumerates the returned artifact types (entity sets, entity types, keys, associations, annotation targets). This clearly distinguishes it from sibling tools such as download_odata_service_metadata or query_odata_data.

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 word 'local' establishes the main intended scenario: analyzing a metadata.xml file that already exists locally, which implicitly excludes remote OData service discovery. However, it does not explicitly name alternative tools or state when not to use this tool, so it stops short of full exclusion guidance.

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