create_filesystem_pathexists

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

Annotations indicate readOnlyHint:false, idempotentHint:true, destructiveHint:false, but the description adds no behavioral context. It does not explain what the tool does (e.g., checks path existence, creates a record, etc.), whether it has side effects, or what the response looks like. With such minimal annotations, the description carries the full burden and fails to disclose any behavior beyond the endpoint.

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 short (two lines) but under-specified rather than concise. It lacks essential information, so brevity is not a virtue here. The structure is minimal but does not front-load useful details; it only gives a generic 'Create or act' and an endpoint.

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 ambiguous name and the open-ended body parameter, the description is grossly incomplete. It does not explain what the tool accomplishes, what the request body should contain, or what the response will be (even though an output schema exists, the agent cannot infer the input). This is inadequate for an agent to invoke it 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 only parameter is 'body' which is an open object (additionalProperties true) with no schema description. Schema coverage is 0%. The description tells the agent to read the GET or /schema endpoint to find fields, deferring responsibility rather than providing any meaning. This provides no value beyond the schema's empty 'body' definition.

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 says 'Create or act on filesystem pathexists' which is vague and ambiguous. It does not state a specific verb like 'check' or 'verify' and the resource 'pathexists' is not clarified. It gives an endpoint but that alone does not explain the tool's purpose. It does not distinguish from siblings, though none are similar, but it fails to provide a clear function.

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 guidance on when to use this tool vs alternatives. The description does not mention any context, prerequisites, or exclusions. It simply points to the endpoint and tells the agent to read the GET or /schema endpoint, which is not usage guidance.

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