aiworkhub_manager_context_import

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, but it says nothing about permission requirements, destructive effects, reversibility, idempotency behavior (despite an idempotency_key parameter), or what 'legacy context store' mutation entails. It only signals that three operations exist, which is minimal context.

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 definition is a single, front-loaded sentence with no filler. It is concise, though its brevity comes at the cost of completeness.

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 complex mutation/import tool with seven parameters, no annotations, and an output schema present, the description is far too thin. It does not cover required auth, safety of dry-run versus apply versus rollback, idempotency, or the meaning of source_path and component.

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%, so the description must compensate for all seven parameters. It only repeats the operation enum values (dry-run, apply, rollback) and provides no meaning for component, source_path, provenance, limit, import_id, or idempotency_key, leaving nearly all parameter semantics unexplained.

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 states a specific resource ('one explicit repo-local legacy context store') and enumerates the three operations (dry-run, apply, rollback), which is more than a tautology. It does not explicitly name 'import' as the verb, relying on the tool name, and does not directly distinguish itself from the many other context-related siblings.

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 given about when to choose this tool versus alternatives, nor are any prerequisites or exclusions mentioned. The description only lists operations, leaving the agent to infer the use case entirely.

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