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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description adds real context on top: newest-first ordering, verbatim content, and that paging continues via a hint at the end of the response. It does not mention volume or size limits per page, which is the only notable gap.

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?

Three compact clauses, each doing distinct work: what the journal is, when to call it versus the alternative, and how to page. Front-loaded and free of filler.

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?

An output schema exists, so return values need not be described, and the description still adds the paging-in-response detail an agent needs to iterate. Combined with readOnlyHint annotations, nothing essential for correct invocation is missing.

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 carry the load, and it explains offset meaningfully (0 = freshest, then page following the hint in the response) rather than restating the type. project_id is left unexplained but is self-evident from the tool's resource.

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?

States the specific resource (the project journal), what it contains (session summaries and milestone notes), and its ordering (newest first, verbatim). The phrase 'Зови за «что было N сессий назад»' plus the explicit hand-off to search_project makes it unmistakable against its siblings.

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?

Gives an explicit use case ('what happened N sessions ago') and names the alternative tool for the competing need (topic search -> search_project). The condition that selects each tool is stated rather than inferred.

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