ms_read_text

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It signals a read-only operation via 'Read' and confines access to the work root, but it says nothing about maxBytes truncation, nonexistent files, non-text content handling, or whether any side effects occur.

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 a single, direct sentence with no filler and the core action is front-loaded. It is concise, though the brevity partly reflects under-specification rather than a deliberate balance of completeness.

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 annotations, the description must explain what the caller receives and how the tool behaves at boundaries. It does not mention the return value, truncation due to maxBytes, error behavior, or path restrictions beyond the vague 'work root.' For a two-parameter tool in a large sibling set, this is inadequate.

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?

Schema description coverage is 0%, so the description must compensate. It adds some meaning to 'file' by identifying it as a text output file under the work root, but it leaves 'maxBytes' entirely unexplained, including its default, maximum, and truncation behavior. This is only partial compensation.

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 states a specific verb and resource: 'Read a text output file under the MS-MCP work root.' It clearly identifies the tool's function, though it does not explicitly differentiate it from sibling tools. None of the listed siblings appears to be a generic text-file reader, so the purpose is reasonably distinguishable.

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?

The description provides no when-to-use guidance or alternatives. It only constrains the file location to 'the MS-MCP work root,' which is a scope restriction rather than usage guidance. An agent is not told when to choose this tool over related status or GUI inspection tools.

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