d365fo_get_database_schema

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

With no annotations, the description carries the full burden of behavioral disclosure. It accurately describes the tool as a read-only operation returning schema information and lists the data categories. It does not mention potential performance impacts or limitations, but given the nature of the tool, this is acceptable.

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 well-structured with bullet points for the returned information, a clear usage statement, and a parameter list. It is concise yet complete, with no superfluous sentences.

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 no output schema and no annotations, the description adequately covers purpose, parameters, usage context, and return value. It provides enough information for an AI agent to correctly select and invoke the tool.

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?

The input schema has 0% description coverage, so the description fully compensates by explaining each parameter: table_name for specific tables, include_statistics, include_indexes, include_relationships as boolean flags, and profile with its default behavior. This adds essential semantic meaning beyond the 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?

The description clearly states that the tool retrieves comprehensive schema information for the D365FO metadata database, listing specific details like tables, columns, indexes, foreign keys, and statistics. This specificity distinguishes it from sibling tools like d365fo_get_database_statistics or d365fo_get_table_info, which have narrower focus.

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 advises using this tool to understand the database structure before writing SQL queries, providing clear context for its use. It does not explicitly state when not to use it or list alternatives, but the guidance is sufficient for an AI agent.

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