memory_batch

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

With no annotations, the description fully discloses behavior: returns joined files with headers, handles missing/invalid paths inline without exceptions, raises ValueError for invalid args, returns empty string for empty list. Transparent about internal constant _MAX_BATCH_PATHS.

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?

Concise two-paragraph description, no redundancy. Front-loaded with purpose, then clear parameter descriptions. Every sentence adds value.

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?

Given the simple parameter (one array) and existence of output schema, the description covers input expectations, return format, error handling, and edge cases (empty list, missing files). Complete for this 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 coverage is 0%, but description adds meaning: 'paths' is a list of relative paths with a maximum count, and explains format. Provides enough context beyond the bare 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?

The description clearly states it reads multiple palace files in a single call, specifying the action (read multiple) and resource (palace files). It differentiates from siblings like memory_read (single file) and memory_write (write operation).

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?

Provides context on when to use (batch reading) and behavior details (max paths, partial results). Does not explicitly list alternatives but implies usage for multiple files versus single file reads.

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