CreateEntity

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

No annotations exist, so the description bears full responsibility for disclosing behavioral traits. 'Create New Entity' simply restates the operation name and offers nothing about side effects, required permissions, idempotency, response format, or consequences. For a mutation tool this is severely insufficient.

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 extremely short, but it is under-specified rather than concisely informative: every word duplicates the tool name. There is no fluff, but also no added value beyond the title.

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 large sibling set and the absence of annotations or an output schema, the description leaves an agent without information about the result of the call, preconditions, or how this differs from neighboring entity tools. It is minimally viable at best, but substantial context is missing.

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 zero properties, so there are no parameters for the description to clarify. The schema already covers the full interface at 100% coverage, and with 0 params no additional semantic description is needed.

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 specific verb and resource, 'Create' + 'New Entity', indicating a creation operation. However, it does not differentiate from sibling tools like CreateCheckEntity or CreateEntityGetIDVToken, and gives no detail about what constitutes an entity. It is clear at a surface level but lacks distinguishing context.

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 on when to use this tool versus the many sibling creation tools such as CreateCheckEntity, CreateEntityGetIDVToken, or CreateDocument. An agent has to infer selection from the name alone. This is a clear gap in usage guidance.

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