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

Beyond the annotations' safety hints, the description discloses that the action marks content for human review, that nothing is deleted or unpublished, that deletion is intentionally human-only, and mandates a user-facing notification. This materially changes how an agent should behave after calling it. No contradiction with annotations.

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 tight sentences: the first states the operation in verb+endpoint form, the second adds the behavioral and safety constraints. Every sentence carries a distinct, necessary piece of information with no filler.

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?

With an output schema available and annotations covering mutability and destructiveness, the text supplies the one thing the schema cannot: the post-condition ('awaits human review'), the explicit user-communication requirement, and the no-deletion guarantee. Nothing an agent needs to invoke it correctly 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?

All three parameters are fully documented in the schema (100% coverage), and the description only reinforces the reason parameter's purpose ('outdated/incorrect') without adding format or edge-case guidance the schema lacks. Baseline of 3 is appropriate when the schema does the heavy lifting.

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?

Description opens with a specific verb and resource: 'Flag a memory as outdated/incorrect' and includes the exact endpoint (POST /memories/{id}/flag). It distinguishes from sibling tools by clarifying this is a review-flagging action that does not delete or unpublish, so an agent won't confuse it with update or listing tools.

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?

It clearly states the tool's role ('marked for human review') and gives an explicit agent directive ('ALWAYS tell the user a memory awaits their decision in the panel'). However, it never references sibling tools or states when NOT to use it, leaving alternative selection implicit.

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