create_entity

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

With no annotations provided, the description carries the full burden. It describes the creation action and required fields but does not mention side effects, authentication requirements, idempotency, or return value. Basic purpose is clear but behavioral context is lacking.

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 concise: two sentences that front-load the core purpose and then immediately state the constraint. Every word is necessary and no filler is present.

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 tool has 6 parameters and an output schema exists, the description covers the minimum viable information to create an entity. However, it could be more complete by mentioning default values (e.g., entity_type defaults to 'company') or the relationship with the batch variant. It is adequate but not rich.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds value by highlighting the dependency between name, description, and additional_attributes.company_attributes.domain, but does not explain other parameters like api_key or entity_type 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 'Create a single entity (a company or person)', which is a specific verb and resource. It distinguishes from siblings like create_entities_batch (batch creation) and other entity tools.

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 specifies required fields (name plus one identifying field) but does not provide explicit guidance on when to use this tool versus alternatives like create_entities_batch or update_entity. Usage context is implied but not fully fleshed out.

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