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

The only behavioral hint is 'body discarded', which suggests content beyond the instruction count is not preserved or inspected. But with no annotations provided, the description fails to disclose whether the tool is a read-only check, how it errors, or what side effects (if any) exist—leaving an important part of the behavior hidden.

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 very short, but the phrase 'Dockerfile instruction count, body discarded' is not a clear, front-loaded statement; it is an incomplete fragment. It lacks any structure that highlights the main 'does the tool do x' pointer, and the brevity results in under-specification rather than effective conciseness.

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?

This tool has a generic 9-parameter schema with no output schema and no annotations, so the description must do a lot of work. It leaves out the return format, usefulness of each parameter, and the specific purpose in the context of the whole tool set, making it impossible for an agent to know how to invoke the tool correctly.

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 input schema coverage is 100%, and each parameter includes a description, so the structured data covers the parameters. However, no description links any of those parameters (e.g., path, ref, url) to the Dockerfile instruction counting, leaving the parameter selections. The tool description adds no extra meaning and does not bridge the gap between the scheme and the purpose.

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 'Dockerfile instruction count, body discarded' refers to a resource (Dockerfile) and an action (counting instructions), but it does not state a clear predicate: it gives no verb, no explicit output, and no explanation of 'ok'. It also fails to distinguish the tool from many sibling shape/check tools, leaving the purpose vague.

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 contains no guidance about when to use this tool versus any of the sibling tools. There are no explicit alternatives, no conditions, and no context about typical use-cases, so an agent has to rely solely on the tool name.

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