set_base_resume

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

With no annotations provided, the description carries full burden. It discloses that the tool overwrites the base resume and affects validation, but lacks detail on permissions, error states, or consequences for existing tailored resumes. This is adequate but not comprehensive.

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 two sentences with no fluff. Every word adds value: specifies action, input format, and behavioral consequence. Front-loaded and concise.

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 simple single-parameter tool with no output schema or annotations, the description adequately covers purpose, input, and effect. However, it could mention the return value (e.g., success or error) or any required preconditions for completeness.

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 single parameter resume_json is described similarly in both schema and description ('Full base resume JSON as a string'). The description adds the context that it must be the full resume, not partial, which provides some extra meaning beyond the schema's description.

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 verb 'Replace' the 'bundled base resume' with a new one, and specifies that it becomes the new source of truth for validation. This distinguishes it from siblings like get_base_resume (retrieval) or save_tailored_resume (saving tailored versions).

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 implies usage when you want to update the base resume and notes its role in validation, but does not explicitly state when not to use it (e.g., for viewing or partial updates) or mention alternatives like get_base_resume for retrieval.

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