search (query-based discovery) vs read (fetch an exact path/ID) vs write vs invoke_sdk_cap are largely distinct actions, and descriptions clarify the file-vs-SDK-capability duality. However, search and read both span files and SDK capabilities, creating mild overlap an agent could occasionally confuse when deciding whether to look up or fetch a record.

Three tools use terse single verbs (search, read, write) while one uses a fuller verb_noun form (invoke_sdk_cap); all are lowercase snake_case and verb-first. The pattern is readable and mostly consistent, with the one longer name being the only deviation.

Four tools is compact but each earns its place: discovery, read, write, and remote capability invocation cover the core surface of a file+SDK server. It is on the thin side but defensible for the focused scope.

The set exposes read, write/append (idempotent overwrite), search, and SDK invocation, but no delete or directory/list mutation is offered despite the file-oriented surface. Missing delete and any explicit listing/management operation is a notable gap agents will hit when housekeeping files.