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

With readOnlyHint=true already signaling no mutation, the description adds meaningful behavioral context by detailing what is produced: complete AxDataEntityView XML with data sources, field mappings, entity key, IsPublic/PublicEntityName, and staging table template. It also notes the use of real field names and relations from the local model.

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 front-loaded with the WHEN trigger, then output details, then the critical prerequisite. The trigger phrase list is long but serves a useful routing purpose; overall, every sentence contributes information without meaningless filler.

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 6-parameter tool with no output schema, the description covers the artifact produced, its contents, the source model, and the mandatory pre-check. It is sufficient for correct invocation, though it could add a note about what happens if a standard entity already exists.

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 input schema already documents all six parameters well. The description adds some context around IsPublic/PublicEntityName and field mappings, but it does not materially extend the schema's parameter-level explanations.

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 tool generates AxDataEntityView AOT XML from a table for OData/DMF/data migration, with a specific resource and output type. It also differentiates this from siblings like get_data_entity_info and create_aot_object by naming the exact XML artifact and use case.

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, provides concrete trigger phrases, and instructs 'ALWAYS call find_entity_for_table first to verify a standard entity doesn't already exist.' This gives clear routing and an explicit alternative/check before using the tool.

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