reading_read_submission

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

The readOnlyHint annotation already signals a safe read operation, and the description does not contradict it. The description adds some useful context by stating the returned content includes 'notes and context,' but it does not disclose further behavioral details such as response shape, pagination, or side effects—though none are expected for a simple read.

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 a single, front-loaded sentence with no filler words. It efficiently communicates the core action and content focus, though it is terse enough that some detail is sacrificed.

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 single-parameter read tool with a readOnlyHint, the description is minimally adequate: it states what is read and what is included. However, with no output schema and no guidance about where submissionId comes from or what 'context' means, the description leaves notable gaps for an agent that must 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?

With schema description coverage at 0%, the description needed to compensate for the lack of parameter documentation, but it never mentions 'submissionId' or explains how to obtain or format it. The parameter name is self-descriptive and the tool name reinforces the concept, but the description adds little semantic value beyond that.

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 ('Read') and resource ('one human note submission batch') and clarifies the payload includes 'notes and context.' It is clear enough to be distinguished from the sibling 'reading_list_submissions' by the singular 'one,' though it does not explicitly name an alternative.

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 phrasing implies this tool is for reading a single submission batch, but it provides no explicit guidance on when to use it versus reading_list_submissions or other related tools. There are no stated exclusions or alternative routing, leaving the agent to infer usage context.

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