edit_entity

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

Discloses key behaviors: id is immutable, thread label synced on promotion, aliases replace existing list. No annotations provided, so description carries the burden well, though missing auth or rate limit info.

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?

Two sentences plus a bullet list, front-loaded with purpose, no redundant words. Every sentence adds value.

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?

Adequate for a simple mutation tool with no output schema. Covers inputs and behavioral traits. Could mention success/failure response, but not critical.

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?

With 0% schema description coverage, the description fully explains all three parameters: entity source from list_entities, name and aliases are optional with clear semantics (replacement for aliases). Adds value 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?

Clearly states the tool renames an entity or replaces its aliases, specifying the verb and resource. Distinguishes from sibling tools like edit_note or edit_stream by focusing on entity identity and aliases.

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?

Implies usage for renaming or changing aliases, but lacks explicit when-to-use vs alternatives such as promote_entity or edit_stream. No mention of prerequisites or conditions.

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