start_reading_mode

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

Annotations declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the agent knows it mutates local state non-destructively. The description adds nothing beyond that: it doesn't say what keys get remapped, whether the change persists after the session, whether evremap must be installed, or how the mode is exited.

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?

It is a single compact phrase with no padding, but it is terse to the point of under-specification for a state-changing system tool; the one clause present does little work.

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?

With no output schema and no parameters, the description carries the full explanatory burden for a mode-switching tool, yet it never says what entering reading mode changes, whether it can be reverted, or what the agent should expect afterward.

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 tool takes zero parameters, so there is nothing for the description to clarify; the baseline for a parameterless tool applies.

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 verb 'start' and resource 'key remapping for reading mode' are stated, and the parenthetical '(evremap)' hints at the underlying tool. However, 'reading mode' and what the remapping actually does are never defined, so an agent knows the general category but not the effect.

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?

No when-to-use guidance, prerequisites, or alternative given. The obvious counterpart stop_reading_mode exists in the sibling list but the description never references it or states that this toggles into a mode the sibling exits.

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