init_profile

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

Annotations already declare destructiveHint=false and openWorldHint=false, so the safety profile is largely covered. The description adds genuinely new behavior: it refuses an existing profile, overwrites nothing, and names the returned key ('created': the files written). It stops short of describing failure ordering or permissions, hence 4 rather than 5.

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, each earning its place: purpose, usage/alternative, safeguards and return. The most decision-relevant content (what it creates and when to call it) is 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?

No output schema exists, but the description compensates by naming the returned field. Combined with the refusal/no-overwrite guarantees and the pointer to import_profile, an agent has everything needed to call this correctly in one shot.

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 100% and the single parameter is already fully documented ('Folder to create. Must not hold a profile yet.'). The description adds a return-value note rather than parameter meaning, so the schema carries the load and 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 ('Create a new profile folder') and enumerates the artifacts produced (profile, bullets, skills, variants YAML templates). It also distinguishes itself from the sibling import_profile, which imports existing data rather than scaffolding empty templates.

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?

Explicit timing ('Use it once, before anything else, when the person has no profile') plus a named alternative and the condition that selects it ('to start from LinkedIn or a JSON Resume, call import_profile afterwards'). The precondition is unambiguous.

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