d365fo_delete_entity_record

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

No annotations are provided, and the description only says 'Delete a record,' implying mutability but offering no details on side effects, permanence, required permissions, or error conditions. The return type is vaguely described as 'dictionary with deletion result.'

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 concise, with a clear introductory sentence followed by structured Args/Returns sections. No unnecessary words or redundancy.

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?

The description covers parameter meanings and return type, but given no annotations or output schema, it lacks completeness on error handling, authentication needs, and edge cases (e.g., deleting non-existent records). It is adequate for basic usage but not fully comprehensive.

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 lacks descriptions (0% coverage), but the description's Args section provides meaningful explanations for all four parameters, including examples for entity_name and clarifying composite keys. This adds significant value beyond the schema's titles.

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 'Delete a record from a D365 Finance & Operations data entity,' specifying the action and resource. It distinguishes itself from sibling tools like d365fo_create_entity_record and d365fo_update_entity_record, and there is no other delete record tool.

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 provides no guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. It simply states what it does without context on appropriate use cases.

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