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

With no annotations, the description carries the full behavioral burden and does a fair job: it discloses the org:admin permission requirement, the policy-dependent branch, and the concrete return shape (status=pending_review plus review_id). It omits what happens to the prior kind, whether the change is reversible, and idempotency, but the disclosed behaviors are substantive and above baseline.

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 short paragraphs, front-loaded with the core action, followed by only the conditional behavior an agent needs. No filler, no repetition of the name, and the review branch is clearly separated.

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?

An output schema exists, so return values need not be fully described, and the mention of status=pending_review/review_id adds useful pointer context. Combined with the permission and policy disclosure, this is close to complete for a bounded mutation; only reversibility/conflict semantics are 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?

Schema description coverage is 100%, so each parameter (slug, kind, kind_name, agent) is already documented in the schema, with kind explicitly noted as an alias for kind_name. The description adds no parameter-level meaning beyond that, so the baseline 3 is appropriate.

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?

It states a specific verb and resource: 'Change the object kind of an existing ontology entity.' That is unambiguous. However, it never distinguishes itself from closely related siblings like memory_ontology_object_kind_set, memory_ontology_propose_entity, or memory_ontology_merge_entities, so the agent must infer scope from the name alone.

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 gives real context: it requires org:admin, and under a 'review' entity_proposals policy it defers to a rekind review instead of mutating directly. That implies when the tool will act vs. defer. But there is no explicit 'use this instead of X when Y' guidance against alternatives such as object_kind_set or propose_entity, leaving the caller to guess.

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