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

The description discloses several behaviors beyond the annotations: everything lands as a proposal, never as an active rule; pinning is deliberately not done because it spends reading budget; malformed documents cause a total refusal with a count of omitted units. This is rich behavioral disclosure that goes far beyond the simple annotations (readOnlyHint false, destructiveHint false). No contradiction with annotations.

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 front-loaded with the main action, then explains the proposal status, pinning, and atomicity. Each sentence adds information, though it is fairly long. It is well-structured, not padded, and every sentence contributes to understanding the tool's behavior.

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?

The description covers the main behavioral aspects, parameter guidance, and edge cases (malformed documents). It does not mention the return value, but no output schema exists, so the description could have addressed that. Overall it is fairly complete for the tool's complexity.

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?

The schema already describes both parameters with 100% coverage. The description adds critical context: the pack must be read and passed as an object (not a URL), and the project slug must be verified against the roster. This adds meaning beyond the schema and helps the agent avoid common mistakes.

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 opens with a specific verb and object: 'Bring a memory pack into a project.' It then clarifies the outcome (everything lands as a proposal, never an active rule) and distinguishes the tool from siblings like arroway_export by stating what it does not do. This is not a tautology and is immediately understandable.

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?

The description gives clear context for when to use this tool: when you have a memory pack to bring into a project. It sets expectations that the pack is never activated, so it is for importing as proposals. It does not explicitly name alternatives, but the purpose is clear enough for an agent to infer when to choose it. It also hints at verification of the project slug, which is useful guidance.

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