status

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

The annotations already declare readOnlyHint=true and openWorldHint=true, which cover the safety profile. The description adds meaningful context by specifying that the tool verifies both the presence of OVERLEAF_SESSION and its validity as an Overleaf login, going beyond what the annotations alone communicate.

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?

A single, direct sentence that immediately states the tool's purpose. No filler or redundant content, and the core check is front-loaded.

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?

For a zero-parameter status tool with readOnlyHint=true, openWorldHint=true, and an output schema available, the description fully covers what the tool does. There are no missing preconditions or parameters to explain, so the agent has what it needs to invoke it correctly.

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 tool has zero parameters, so the schema requires no parameter documentation. The description correctly focuses on the operation itself; with no parameters, the baseline of 4 applies.

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 uses a specific verb ('Check whether') and a clear resource ('OVERLEAF_SESSION' and 'valid Overleaf login'). It clearly differentiates this tool from the project/file/compile siblings since it is the only auth/status check.

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 intended use is implied as a preflight authentication check before interacting with Overleaf, but the description does not explicitly say when to use it versus alternatives or when it should be run. There is no exclusion or mention of prerequisites, leaving the agent to infer the usage context from the sibling tool names.

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