list_parse

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds the concrete endpoint (GET /api/v3/parse) which confirms the HTTP method and path. No behavioral contradiction; the bar is lower because annotations carry the burden, and the description adds a small amount of useful contract detail.

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 lean and front-loaded, showing the endpoint first followed by the parameter roles. Every line earns its place. It's terse to the point of sparseness, but as a purely structural matter it is well-organized and free of waste.

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?

The tool is simple (2 optional string params) and has an output schema, so return values are documented elsewhere. The main gap is that the description never clarifies what the Parse resource is, which is essential context for an agent deciding whether this tool applies to its task. The interaction between title and path is also unexplained.

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 compensate. It does add one piece of meaning beyond the schema: it labels title and path as 'Query parameter,' which tells an agent how to pass them (query string rather than body). However, it doesn't explain what these parameters semantically mean — what a valid path or title looks like, or whether they are alternatives or combined filters.

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 'Read Parse' is essentially a restatement of the name 'list_parse' — 'list' maps to 'Read' and 'parse' is the resource. It confirms the GET action but never explains what the Parse resource actually is or what data it returns, leaving an agent guessing about the tool's function.

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?

No usage guidance is given. There are dozens of sibling list_* and get_* tools, but the description doesn't say when to use list_parse versus alternatives, nor does it clarify what scenario this tool addresses (e.g., is it for previewing a title/path parse before saving?). It's neither misleading nor helpful.

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