BlacklistEntity

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

No annotations are present, so the description carries the full burden of behavioral disclosure. 'Set' implies a mutating write operation, but nothing is disclosed about side effects, reversibility, permission requirements, or what values the blacklist state can take — a significant gap for a mutation tool.

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 four words — 'Set Entity Blacklist State.' — front-loaded with the verb and free of any filler. Every word earns its place; the terseness is a completeness problem, not a conciseness problem, and is scored elsewhere.

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?

For a zero-parameter, no-output-schema tool this is nearly complete, but the semantic gap versus WatchlistEntity, the unstated mechanics of what blacklisting does, and the unexplained absence of parameters to identify the target entity leave an agent guessing about correct invocation.

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?

The input schema is an empty object with zero parameters, so there is nothing the description needs to add beyond the schema. The vacuous 100% coverage and zero-param baseline apply; the description loses no points here, though it also never explains how the target entity is identified.

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 a clear verb and resource: it sets the blacklist state of an entity. This separates it from obvious siblings like CreateEntity, DeleteEntity, and SearchEntity, but the semantically close sibling WatchlistEntity is not differentiated, leaving some ambiguity about what distinguishes blacklisting from watchlisting.

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 given on when to use this tool versus alternatives. Siblings like WatchlistEntity and UpdateEntityState overlap semantically with this tool, and the description does not name any alternative, exclusion, or condition that would help an agent pick between them.

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