notify and notify_file have clearly different nominal purposes (text vs file), but notify_file is permanently disabled, so an agent has a real chance of wasting a call on a dead branch before reading the caveat. With only one functional operation, the distinction is trivial rather than a genuine choice.

Both names are lowercase snake_case and share the 'notify' stem, which is predictable. Minor deviation: 'notify' is a bare verb while 'notify_file' adds a noun, so the pattern is more a prefix family than a strict verb_noun scheme.

Effectively one usable tool, since notify_file is refused on every call. For a single-purpose one-way notifier that is defensible, but advertising a non-functional second tool makes the surface feel padded and thin at the same time.

The core send-a-message operation exists, but file sending is exposed yet permanently off, and there is no recipient selection, no read/status, and no message formatting options. The surface has a built-in dead end rather than a coverage gap an agent can work around.