profile_export

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

With no annotations, the description must carry the full behavioral burden. It does disclose one meaningful trait — the resulting profile is flattened with inherited values and is not linked to a parent — but says nothing about whether destination files get overwritten, whether the operation is reversible, or what permissions/locations are required for a tool with 4 required parameters.

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?

One sentence with no filler, so it is concise, but the single sentence carries no operational detail and the most decision-relevant fact (flattening/inheritance) is buried mid-sentence.

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?

An output schema exists so return values need not be described, but for a mutation-style tool with no annotations and 5 undocumented parameters the description is far too thin: the meaning of 'flattened', the source-to-destination relationship, and any side effects remain unexplained.

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 0% across 5 parameters, and the description names none of them. It never explains what 'source' and 'destination' refer to, what 'search_directories' controls, or what 'name'/'profile_version' do, so an agent is left guessing at all required inputs.

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 gives a verb and resource ('Create a new flattened user profile'), but it sits awkwardly against the tool name 'profile_export' and the source/destination parameters, which imply copying an existing profile somewhere. An agent cannot confidently tell whether this exports, copies, or creates from scratch without opening the schema.

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?

There is no guidance on when to use this versus sibling tools such as profiles_list, profile_resolve, or host_plugin_export/host_project_export. The 'no parent dependency' clause hints at a use case but never states a condition for selection.

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