get_review_data

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

With no annotations, the description carries the full behavioral burden. It discloses that this is a broad composite read, lists the contents it returns, and fully specifies how logbook_period behaves. It does not explicitly say 'read-only' or warn about payload size, but the 'get' semantics make the behavior clear enough.

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 compact: it front-loads the purpose, lists bundled content in a single line, and reserves a short 'Args' block for the one parameter. Every sentence earns its place with no filler or tautology.

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?

It covers the tool's return scope and the only parameter well, and there is no output schema requiring elaboration. It stops short of a 5 because the description never hints at the exact response shape or the potentially large payload of such an aggregate call, which would help an agent set expectations.

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 schema only defines a default string, so the description compensates completely by explaining the meaning, default value, format pattern (Nd/Nw/Nm/Ny), and concrete examples. This gives an agent everything needed to supply the argument correctly.

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 states a specific verb ('Get') and a concrete resource ('all data needed for a weekly/daily review'), then enumerates the bundled categories. This makes it easy to distinguish from sibling tools like get_dashboard or get_context.

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?

It explicitly identifies the intended use case ('weekly/daily review') and frames the tool as a replacement for '10+ separate MCP calls,' so an agent knows to select it for whole-review retrieval. It does not name alternatives or state when not to use it, which prevents a 5.

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