import_persona

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the import action but doesn't describe what happens during import (e.g., validation, error handling, side effects), whether it requires specific permissions, or what the expected outcome looks like. The mention of 'overwrite' parameter hints at mutation behavior, but this isn't elaborated in the description itself.

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 a single, efficient sentence that communicates the core functionality without unnecessary words. It's appropriately sized for a tool with two parameters and no complex behavioral nuances to explain. Every word earns its place in conveying the essential operation.

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 no annotations and no output schema, the description is inadequate. It doesn't explain what constitutes a valid persona format, what validation occurs during import, what happens on success/failure, or what the tool returns. The 100% schema coverage helps with parameters, but the overall behavioral context is missing for a tool that presumably modifies system state.

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 description coverage is 100%, so the schema already fully documents both parameters ('source' and 'overwrite'). The description adds no additional meaning beyond what's in the schema - it mentions 'file path or JSON string' which is covered by the schema's description of 'source', and doesn't elaborate on parameter interactions or constraints. Baseline 3 is appropriate when schema does all the work.

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 action ('Import') and resource ('a persona'), specifying the source types ('from a file path or JSON string'). It distinguishes from siblings like 'create_element' by focusing on importing rather than creating from scratch. However, it doesn't explicitly differentiate from 'install_collection_content' which might involve similar data loading operations.

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?

No guidance is provided on when to use this tool versus alternatives like 'create_element' or 'install_collection_content'. The description lacks context about prerequisites, typical use cases, or scenarios where importing is preferred over other creation methods. It mentions the source format but not when this operation is appropriate.

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