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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), but the description adds meaningful context beyond them: the document is NOT sent to the server, no object list is embedded, and resolve_names must be called ONCE. These are real behavioral facts an agent could not derive from annotations alone. Minor gap: it doesn't describe the return/pass format in detail, though an output schema exists.

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 opening line and the STEP-framing are front-loaded and each step earns its place, giving a usable workflow. It is dense but not padded; the only cost is length from enumerating all four flow stages, which is close to justified for a multi-tool orchestration.

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?

Given a single parameter, an output schema (so return values need no prose) and a read-only annotation set, the description is complete: it covers when to use, the data-flow contract (nothing sent to server), and the required downstream calls. 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?

Schema coverage is 0% for the single `memory` parameter, so the description carries the burden — and it does: '`memory` is the graph's slug from list_my_memories.' This gives both meaning and provenance for the value, which the bare schema property does not. Not a full 5 only because it doesn't state the slug format or a concrete example.

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 gives a specific verb+resource ('Add a document to the knowledge graph by extracting it YOURSELF') and explicitly positions the tool as 'STEP 1 of 4' in a named flow. It distinguishes itself from siblings like resolve_names and submit_extraction_from_llm by describing exactly what each does. An agent can tell this apart from the rest of the toolset without opening a schema.

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 states the precise trigger: 'Use whenever the user shares a document/notes/transcript and wants it captured in the graph, and you (this assistant) should do the extraction.' The 'YOURSELF, in this chat' phrasing implicitly excludes the server-side alternative, and the workflow tells the agent what to do next rather than leaving it to inference.

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