list_parse

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the 'Read'/'GET' wording is consistent with them. The description adds the transport method and the optional query parameter but reveals no additional behavioral traits such as pagination, empty results, or error behavior.

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 content is tightly front-loaded with the verb, endpoint, and arguments in a clear structure; there is no padding. It is concise to the point of under-specification, but as a short tool stub it remains easy to scan.

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-optional-argument read endpoint with an output schema and safety annotations, the description is almost enough to call successfully. However, it lacks the domain purpose of Parse and any behavior details, so an agent has only the resource name and output schema to infer correct usage.

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%, so the description must carry the parameter semantics, but 'title: Query parameter' only tells where the parameter is sent, not what values are valid or how title affects the response. It adds a small amount beyond the schema but does not explain filtering or matching behavior.

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 says 'Read Parse' and the endpoint GET /api/v3/parse, but this essentially restates the tool name 'list_parse' and does not explain what a Parse is or what reading it returns. It identifies a resource and verb but gives no domain meaning, leaving the agent to guess whether this lists parse results, parses titles, or something else.

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?

There is no indication of when to call this tool versus the many sibling list_* tools, and no mention of prerequisites or common workflow context. The endpoint and arg are the only guidance, so the agent cannot know if this is the right tool for a task.

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