read_case_folder

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds useful scope context but does not disclose return format, recursion behavior, or error handling. It adds some value beyond annotations without contradicting them.

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 a single, front-loaded sentence with no filler. It states the action and scope directly and earns its place without redundant wording.

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 simple read-only tool with one parameter and helpful annotations, the description is minimally adequate: it identifies file types and directories. However, it omits details an agent might need, such as what the tool returns, how case_folder should be expressed, and whether the read is recursive. The lack of an output schema increases the need for such context.

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 only parameter, case_folder, has 0% schema description coverage, so the description carries the full burden of explaining it. It does not define the parameter's format, path structure, or required value, and only loosely implies it selects a folder under inputs/ and artifacts/. This is insufficient compensation for the schema gap.

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 uses a specific verb ('Read') and names concrete resources ('md / txt / pdf / docx under inputs/ and artifacts/'), making the tool's purpose clear. It does not explicitly name sibling tools to differentiate them, but the file-scope is specific enough to avoid obvious confusion with list_forums or get_agent_instructions.

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 implies when to use the tool: when an agent needs to read supported file types from a case folder's inputs/ or artifacts/ directories. It provides no explicit exclusions or alternative tool names, so an agent must infer which sibling tools to prefer in related scenarios.

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