check_file

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

With no annotations, the description must carry behavioral weight; it discloses that the operation is offline and read/compute-oriented (word counting), which suggests no mutation. It does not, however, describe output structure, error behavior, or file expectations beyond calling the file 'saved notes'.

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?

A single front-loaded sentence with no filler; the 'Offline' qualifier and the specific section pattern are immediately visible. Every word contributes.

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 one-parameter tool this is near-sufficient: an agent can infer that calling it with a notes file path yields per-section word counts. Still, the absence of an output schema and any mention of return format or failure modes leaves a moderate gap.

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% and the only property is 'path'. The description compensates partially by indicating the path points to a saved notes file containing `### BÖLÜM n` sections, but it omits path conventions such as relative vs absolute paths or accepted file formats.

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?

Description states a specific behavior: counting words per `### BÖLÜM n` section of a saved notes file, offline. This is a concrete verb+resource combination and clearly separates it from the chat-oriented sibling tools.

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 'Offline' prefix implies the tool is appropriate when a local, network-free word count is needed, but it does not explicitly state when to prefer it over alternatives or provide any exclusions. Usage context is implied rather than stated.

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