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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety/scope is covered; the description's contribution is framing the content as normative ('what a contribution must meet') and mandatory reading. It does not disclose what is actually returned (no output schema exists), whether the content is static or versioned, or how long it is – a gap for a tool with no output schema.

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?

Two sentences, both front-loaded and load-bearing: the first says what the content is, the second says when to read it. No filler or restatement of the title.

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-param, read-only lookup the description is serviceable but thin: it never defines the domain vocabulary its siblings rely on ('holes', 'evidence', 'passage', 'record'), nor indicates that the returned rules govern those operations. With no output schema, a note on what the response looks like would raise this.

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 takes zero parameters and the description correctly introduces none, so there is no parameter semantics to explain. Baseline 4 applies for a parameterless tool where nothing is left ambiguous on the input side.

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 names the resource ('the Parse') and states what the content covers: how it works and what a contribution must meet. That is specific enough to distinguish it from the action-oriented siblings (parse_submit_evidence, parse_search, parse_read_record). It stops short of saying explicitly that the tool returns the rules/spec text, leaving the agent to infer the retrieval nature.

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?

'Read before submitting' is an explicit precondition that ties this tool to the submit flow, which is real when-to-use guidance. However, it names no sibling alternative and gives no exclusions (e.g., whether it is also needed before reading a passage or searching), so routing among the other six parse_* tools is only partly resolved.

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