Export profile

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

Annotations only declare readOnlyHint=false and openWorldHint=false, so they don't cover mechanics. The description adds real value by revealing the write target (a file at UhhhhhhReanim/Profiles/<name>.json), but it omits whether an existing file is overwritten, permission requirements, or what the tool returns on completion.

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, front-loaded with the verb and the payload, so it's efficient. The garbled path string is the only structural blemish.

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 single-parameter export with no output schema, the description covers what is exported and where, which is most of what an agent needs. It leaves gaps on result handling and overwrite/conflict behavior that a caller would want before invoking a write tool.

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% (the single param 'name' is documented as 'Profile name'), so the baseline is 3. The description adds a small amount by showing name is interpolated as the filename (<name>.json), but no format, character, or collision semantics beyond the schema.

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?

Specific verb (Export) plus the resource (a profile bundle) and it enumerates exactly which settings are included: theme, movement, wheel favorites, audio. It's clearly distinguishable from reanim_import_profile by direction, though it never names the alternative explicitly. The odd 'UhhhhhhReanim' path segment slightly muddies the target.

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 when-to-use or when-not-to-use guidance. The word 'shareable' hints at intent (sharing/backup), but there is no explicit statement of when an agent should call this versus reanim_import_profile, reanim_backup_savedata, or the list/get tools.

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