The two tools have completely distinct roles: one returns documentation, the other runs commands. There is no realistic way to confuse them, and the descriptions reinforce the required ordering (read_instructions before execute).

Both names are snake_case, but read_instructions follows a verb_noun pattern while execute is a bare verb, and read_instructions is a somewhat unusual verb choice for 'get docs'. Minor deviation only; still predictable and readable.

Two tools is on the thin side, though the pattern is deliberate: a single generic dispatcher plus a docs loader. It avoids a bloated per-command surface, but leaves only one actual capability-bearing tool for the whole domain.

Because execute can invoke any underlying pt command, the surface is nominally broad, and read_instructions is meant to cover discovery. However, there is no structured command enumeration, no typed parameters, and no validation or error contract beyond prose docs, which pushes discovery and correctness entirely onto the agent reading a doc blob.