file_summarize

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions two modes (quick/detailed) with brief explanations, but omits critical details: whether the tool is read-only, what happens if the file doesn't exist, how the output is structured, or any side effects. These gaps reduce transparency significantly.

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 extremely concise—only two sentences. The first sentence states the core purpose immediately, and the second adds crucial mode details. Every word earns its place with no redundancy.

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 tool's simplicity (2 parameters, no output schema, no annotations), the description is incomplete. It lacks information about return values, error handling (e.g., file not found), and does not clarify if the tool modifies anything. An agent might need more context to use it reliably.

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. It explains the 'mode' parameter's enum values ('quick' is pattern-based, 'detailed' is LLM), adding meaning. However, it does not describe the required 'file_path' parameter beyond implying it's the file to summarize. Thus, partial compensation warrants a 3.

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 the verb 'summarize' and the resource 'file purpose', making the tool's function evident. It also distinguishes two modes, which adds specificity. However, it doesn't explicitly differentiate from sibling tools that might also deal with files, like 'convention' or 'scope', leaving slight ambiguity.

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 provides no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, excluded scenarios, or related tools. The agent receives no context about appropriate usage, making it rely on inference.

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