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

Annotations only declare readOnlyHint=false, destructiveHint=false and openWorldHint=false. The description adds substantial non-obvious behavior: additive semantics ('never changes or deletes existing memories'), batch limits (1-25 facts, 1,000 chars each, 20,000 total), an explicit sensitive-data exclusion list, and a warning that server pattern checks are a backstop rather than a complete filter.

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?

Front-loads the when-to-use condition and then packs constraints and exclusions into dense, purposeful sentences. It is long but nearly every clause carries a distinct constraint; only the return-value recount is slightly redundant given the output schema.

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 batch mutation tool with an output schema present, the description covers the approval gate, size limits, exclusion policy, additive behavior, and error-handling guidance ('retry only failed entries, and never say the whole list was saved when some entries were refused or failed'). Nothing an agent needs to invoke or report on this tool 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 description coverage is 100%, so the schema already documents 'fact' and 'box' including the category and length constraints. The description reinforces intent ('each a short standalone statement about the user', 'box files a fact under a category') but adds little beyond what the structured fields already say, so the baseline 3 applies.

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?

States a specific verb and resource ('Saves each entry as a separate memory in the user's Configure profile, in one call') and explicitly distinguishes itself from siblings: configure_profile_remember for a single fact and configure_profile_import for raw material. An agent can route correctly without opening any 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?

Gives explicit triggering conditions ('user asks to save several facts at once, or approves a list of facts you proposed'), a pre-call approval workflow ('show the list and wait for their approval'), and named alternatives for the single-fact and raw-material cases. When-to-use and when-not are both covered.

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