save_master_resume

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

No annotations are provided, so the description carries the full burden. It discloses persistence and returns a confirmation path, but lacks details on update behavior, validation, error handling, or constraints (e.g., size limits). The phrase 'Store or update' implies idempotence but is not explicit.

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 well-structured: a clear first sentence, a helpful block of recommended keys, and a concluding sentence about the flow and return value. Slightly verbose due to the key list, but it's practical and front-loaded.

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 the tool has one nested parameter and an output schema (not detailed in input), the description covers the input structure well but only briefly mentions the return value ('confirmation with the stored path'). Missing details on output format, behavior on overwrite, or error cases. Adequate but not fully complete.

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 defines a single object parameter 'resume' with additionalProperties: true, providing no structure. The description adds significant value by listing recommended keys and their structure (contact, summary, experience, projects, skills, education), though it notes these are recommended, not required.

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 clearly states the tool's purpose: 'Store or update the user's base CV so it persists between sessions.' It distinguishes from siblings by calling this 'step 1 of the flow' and contrasting with load_master_resume and export_resume.

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 step 1 of the flow: set it up once, reuse it for every job.' It implies when to use but does not explicitly state when not to use or provide alternative tool names (though sibling context exists).

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