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

With no annotations, the description carries the full burden, and it does disclose that the tool returns complete instructions identical to what the local server provides on connection. This clearly signals an informational, non-mutating help tool, and no hidden side effects are suggested. The exact output structure is not described, but an output schema exists.

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 sentence with the core purpose front-loaded: 'Полная инструкция по ПАРСИ'. The clarifying clause about the local server is relevant context and adds no unnecessary bulk.

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?

Given the tool has no parameters, an output schema exists, and a help tool should simply return the manual, the description provides sufficient context. An agent can correctly identify the tool's purpose and invoke it without ambiguity.

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 input schema has zero properties, so there are no parameters to document; the baseline of 4 applies. The description adds no parameter-related claims, which is appropriate for a no-argument help tool.

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 clearly identifies the tool as providing the complete PARSI instructions, and the phrase 'та же, что отдаёт локальный сервер при подключении' adds useful context about the source of the manual. However, it doesn't explicitly differentiate it from the sibling parsee_cloud_manual, which sounds similar in purpose.

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 implies that this tool should be used to obtain the full PARSI manual, especially the same one shown on local server connection. It gives no explicit when-to-use guidance or alternatives, so the agent must infer usage from the tool name and description.

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