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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false; the description adds nothing beyond that, notably omitting whether duplicate ids are rejected or overwritten and whether the KB must already exist. With annotations only covering the safety profile, the description should carry the duplicate/auth behavior but does not.

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?

A single front-loaded sentence with no filler. It is efficient, though given seven parameters and a nested metadata object it is arguably under-specified rather than optimally concise.

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 rich schema compensates for most parameter detail and there is no output schema to explain, so the minimal description is workable. However, for a 7-parameter, non-idempotent mutation with a nested metadata object, the complete absence of creation semantics (duplicate handling, required parent KB, metadata usage) leaves real gaps.

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 schema already documents id, title, content, folder, source, metadata, and expiresAt in detail. The description's parenthetical ('note, document, or information piece') loosely gestures at the source enum but adds no syntax or default information beyond the schema, so baseline 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?

States a specific verb ('Add') and resource ('entry ... to a knowledge base'), and parenthetically enumerates the kinds of entries. It is distinguishable from the neighboring neuron_create_knowledge_base and neuron_update_kb_entry, but it never names those siblings to sharpen the distinction.

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?

There is no when-to-use guidance, no prerequisites, and no pointer to alternatives such as neuron_update_kb_entry, neuron_ingest_knowledge, or neuron_upload_document. The agent must infer usage purely from the name.

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