d365fo_get_entity_schema

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

No annotations provided, so description carries full burden. It describes parameters and return but does not disclose side effects (likely read-only), authentication requirements, or error behavior. Lacks transparency for a schema retrieval tool.

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?

Well-structured with Args and Returns sections; purpose is front-loaded. While efficient, the description is slightly longer than necessary, but each sentence adds value.

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?

No output schema and description only says 'Dictionary with entity schema' — vague. Does not explain return structure, possible errors, or handling of invalid entity names. Incomplete for a tool with 5 parameters and no output 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 0%, so description must compensate. It provides detailed, clear explanations for all 5 parameters (entityName, include_properties, resolve_labels, language, profile), including examples and defaults, adding value beyond the raw schema.

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?

Clearly states 'Get the detailed schema for a specific D365 F&O data entity' — a specific verb+resource. It distinguishes from sibling tools like d365fo_get_database_schema and d365fo_get_table_info by focusing on entity schema.

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?

Explains parameters but does not give guidance on when to use this tool versus alternatives like d365fo_get_database_schema or d365fo_get_entity_record. No explicit when-not or context for selection.

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