delete_record

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

With no annotations, the description carries full burden. It discloses that the tool is currently disabled, which is a key behavioral trait. However, it does not elaborate on the destructive nature of deletion, permission requirements, or possible side effects beyond the disabled state. The disclosure is minimal but present.

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 a single, short sentence that immediately conveys the core purpose. It avoids unnecessary words and front-loads the action. Even the parenthetical is succinct.

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 the simple nature of the tool and full schema coverage, the description covers the basic purpose but lacks any guidance on when to use it, what consequences to expect, or alternatives. The 'currently disabled' note is useful but does not compensate for missing usage context.

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 fully describes both parameters (id as 'Record GUID' and entity_set as 'Entity set name'). The description adds no additional meaning beyond the schema, so the baseline score of 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 clearly states the action ('Delete a record from a Dataverse table') with a specific verb and resource. The parenthetical '(currently disabled)' adds status context without obscuring intent. It distinguishes from sibling tools like get_record, update_record, and query_records.

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?

No guidance is provided about when to use this tool versus alternatives. There is no mention of conditions, exclusions, or references to sibling tools for similar operations. The phrase 'currently disabled' implies it should not be used, but does not suggest what to use instead.

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