nexus_block_tag

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

Beyond the annotations, the description discloses that the operation is personal-only, has no public side effect, is reversible, only affects blockable tags, and that preference mutations apply immediately while list reads may lag several seconds. This is rich, useful behavioral context that the annotations alone do not provide.

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 concise and well-structured: the main action is front-loaded, followed by scope, reversibility, an important eventual-consistency note, and the return format. Every sentence adds value without unnecessary verbosity.

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 single-parameter preference mutation, the description covers purpose, side effects, reversibility, constraints, eventual consistency, and return format. Combined with full schema coverage and output schema presence, nothing essential is 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?

The schema already fully documents the sole parameter with type, minimum, and source guidance. The description adds the extra semantic constraint that only blockable tags can be blocked, which helps validate acceptable values 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?

The description states a specific action ('Block a tag'), the resource ('for the current user'), and the effect ('hides matching content'). It clearly differentiates itself from related siblings by emphasizing it is a personal preference with no public side effect and explicitly names nexus_unblock_tag as the reverse operation.

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 provides clear context: this is a personal preference mutation, reversible via nexus_unblock_tag, and only works on blockable tags. It does not explicitly enumerate alternatives beyond the unblock sibling, but the personal-scope framing adequately suggests when this tool is appropriate.

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