Path Exists

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing beyond the literal name — not whether it follows symlinks, how permission-denied or unreachable paths are reported, whether it is read-only, or whether it touches the filesystem at all. With an output schema present the boolean result itself needn't be explained, but zero additional behavioral context for an unannotated tool is a major gap.

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?

One short, front-loaded sentence with no filler or redundancy. It is under-specified rather than bloated, which is penalized in other dimensions but not here.

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 trivial one-parameter tool with an output schema, minimal prose is defensible, so the description is close to adequate. Still missing are path-format expectations and edge-case semantics (broken symlinks, permission errors) that an agent would need to interpret the boolean 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?

Schema description coverage is 0% for the single 'path' parameter, so the description should compensate and does not: it never says whether the path must be absolute, whether relative paths or '~' are expanded, or what form is accepted. It adds no meaning beyond the parameter name.

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 states a specific verb ('Check') and resource ('whether a path exists'), so the operation is unambiguous. It is distinguishable from siblings like get_path_info or create_directory by implication, but the description never explicitly contrasts itself with them.

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?

There is no when-to-use guidance at all: no mention of using this as a guard before copy_path/move_path/delete_path, and no statement about when an agent should prefer get_path_info instead. The agent must infer the intended role of a boolean existence check from the name alone.

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