alcove_knowledge_add_entity

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

With no annotations, the description carries full burden but only says 'Add an OKF Entity.' It does not disclose whether the operation is idempotent, destructive, requires permissions, or any other behavioral traits. This is entirely missing.

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 (one sentence), but this brevity is under-specification rather than conciseness. The single sentence does not provide enough value to justify the lack of detail.

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 high parameter count (9) and no annotation, the description is severely incomplete. It lacks context about the entity concept, usage within the knowledge system, and how this tool relates to others. The presence of an output schema does not compensate for the missing 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?

Schema description coverage is 0%, meaning the 9 parameters have no descriptions in the schema. The tool description does not explain any parameters, leaving the agent guessing the meaning of fields like 'kind', 'tags', 'source_refs', etc.

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 states 'Add an OKF Entity' with a clear verb and resource, but fails to clarify what an OKF Entity is or how it differs from sibling tools like add_note and add_question. The jargon 'OKF Entity' is not explained, and the context of similar tools suggests a need for clearer differentiation.

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 alternatives such as alcove_knowledge_add_note or alcove_knowledge_add_question. There is no mention of prerequisites, context, or when not to use it.

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