create_entity

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

There are no annotations, so the description must disclose behavioral traits on its own. It only states the action without revealing side effects such as provisioning time, potential validation failures, or whether the operation is asynchronous. While not misleading, it is far from transparent.

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?

One short, front-loaded sentence with no wasted words. It states exactly what the tool does without redundancy, earning a top score for efficiency.

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 schema is exceptionally rich, covering parameter types, dependencies, and side-effect warnings (e.g., one-way date_behavior). The description itself is too thin to be fully self-sufficient, but when combined with the schema, an agent has nearly everything needed. Still, it could mention high-level constraints like permission requirements or the structural impact of creating an entity.

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 100% description coverage, including detailed comments on enums, mutual exclusions, and defaults. The description itself adds no parameter detail, but the schema already carries the weight, fitting the baseline-3 rule for high coverage.

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 uses a clear verb + resource structure: 'Create a new Dataverse table (entity) with specified attributes.' It unambiguously distinguishes itself from sibling tools like create_record or add_attribute by naming both the table and the ability to pass attributes in the same call.

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 explicit when-to-use or when-not-to-use guidance is provided. The description does not mention how this tool relates to create_record or add_attribute, and there are no exclusions or alternative scenarios to help an agent decide between them.

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