setup_profile

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

With no annotations, the description carries full burden. It discloses the persistence path (~/.config/runway-mcp/profile.json), the failure condition on existing profile, and the return type (ProfileSetupResult). Does not contradict any annotations (none provided). Could add more detail on idempotency or permissions, but current detail is sufficient.

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?

Description is well-structured with a clear purpose statement, prerequisites, behavior notes, and parameter/return sections. It is slightly verbose but not wasteful. Front-loaded with the core verb.

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 no annotations and presence of output schema, the description explains key aspects: prerequisite, failure mode, file path, and return behavior. It adequately covers the tool's usage for an AI agent to decide and invoke correctly.

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?

Only one parameter (profile). The description does not add meaning beyond the input schema, which already includes detailed descriptions for each field and sub-object. Baseline 3 is appropriate since schema coverage is effectively high due to embedded descriptions.

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?

Clearly states the tool's purpose: 'Save a structured profile extracted from the user's CV.' Provides specific verb (save) and resource (profile), and distinguishes from sibling tools by noting it fails if profile already exists, pointing to update_profile as the alternative.

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?

Explicitly instructs to read the CV before calling, and explains the failure condition and alternative tool: 'Fails if a profile already exists — use update_profile to replace it.' This provides clear context on when and when not to use it.

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