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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, but the description adds genuinely new behavior: plan-tier gating (Professional), a 30-day post-downgrade grace period for reads, and outright refusal afterward. That is context an agent cannot get from the annotations, though response size/large-payload characteristics of the serialised JSON are unmentioned.

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 core purpose and return payload are front-loaded in the first two sentences, and every sentence carries information. The licensing sentence is dense and slightly convoluted ("unless baselines are set to Professional; then it needs Professional or above"), costing some readability.

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?

There is no output schema, yet the description explains the returned payload (serialised snapshot JSON with tasks, hours, dates). Combined with the licensing caveat, this covers nearly everything needed for a one-parameter read tool; only the id's expected format and payload size/limits are absent.

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% and the single baselineId parameter is undocumented in the schema, so the description carries the load. It clarifies that the id refers to a project baseline row rather than a project, but adds no format, example, or accepted-value details.

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?

"Full baseline snapshot for one project baseline row" states a specific resource and scope, and the follow-up clause specifies exactly what is returned (tasks, estimated hours, dates at capture) plus the purpose (variance tracking). An agent can tell this apart from capture_baseline (write) and compare_baseline (diffing) without opening the schema.

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 usage for variance tracking and makes clear this is a read of a single row, but it never states when to pick this over compare_baseline or get_row_history, nor names an alternative. The licensing rules describe eligibility, not selection guidance.

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