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

With no annotations, the description carries the full behavioral burden. 'Each lives once' hints at dedup/idempotent re-materialization, but it is too cryptic to state whether re-importing duplicates or updates, what happens on conflicting bundles, or what role verify_signature plays. Permissions and failure behavior are unaddressed.

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?

A single front-loaded sentence with the action first, which is appropriate. The bracketed '[KEEP · internal]' marker adds no value to an invoking agent but costs little.

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-style import tool with no annotations, no output schema, a nested payload object, and 0% parameter documentation, the description does not do enough. It omits the signature-verification option and the meaning of `key`, leaving the agent under-equipped to call it 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?

Schema description coverage is 0% for 3 parameters including a nested bundle object. The description loosely ties 'study bundle' to the bundle parameter, but says nothing about `key` or `verify_signature`, so the two most opaque parameters remain entirely undocumented in both schema and description.

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 names a specific verb (Import) and resource (an exported study bundle) and adds the outcome ('re-materializes its cards'), which is enough to distinguish it from study_export and study_find. It stops short of explicitly contrasting with those siblings, and the '[KEEP · internal]' tag is noise rather than clarification.

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 statement of when to use this tool versus study_export, study_create, or study_find, and no prerequisites or exclusions. The pairing with 'exported study bundle' faintly implies usage but leaves the agent to infer the trigger condition.

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