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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuinely new context beyond the annotations: it uses the connected Himalayas account with no extra sign-in, which is useful auth information. It stops short of stating that supplying content overwrites the existing cover letter text entirely.

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?

Three sentences, front-loaded with the operations, followed by the routing note and the auth note. No filler; each sentence carries distinct information.

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 mutation tool with annotations covering safety and no output schema, the description covers operations, the excluded resume-editing case, and auth. The main residual gap is not spelling out that content replacement is a full overwrite, but that is minor against the existing hints.

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 75%, so the schema already documents id, type, title and content. The description still adds mapping value by tying 'rename' to title and 'replace text' to content, and by reinforcing that content is cover-letter-only. The anyOf id/type semantics are left to 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 names specific verbs and resources: rename a resume or cover letter, or replace a cover letter's text. It also carves out what this tool does NOT do (resume content editing), letting an agent separate it from get_document, delete_document, and the resume editor path.

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 gives a clear when-not: resume content must be edited in the website's resume editor, reachable via list_documents. That routes the agent away from a wrong invocation, but it never names an alternative for renaming or states prerequisites (e.g. that the document must already exist).

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