lithtrix_blob_parse

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

No annotations provided, so description carries full burden. It mentions the endpoint, authentication requirement, and async option but lacks details on side effects (e.g., whether parsing modifies state), rate limits, error handling, or response format. The description is too minimal for a zero-annotation scenario.

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?

Single sentence efficiently packs endpoint, purpose, async usage, callback note, and auth requirement. No redundant words, front-loaded with the essential action.

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?

No output schema and no description of return format or behavior. The tool likely returns parsed data or a reference for polling, but the description does not explain the workflow. Given the existence of lithtrix_blob_parse_status, the description should clarify the relationship, which it does not.

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 coverage is 100% with detailed parameter descriptions. The tool description adds that async=true is for QStash, which slightly supplements the schema's 'async parse + poll'. However, for callback_url, the description just repeats the schema info. Baseline 3 is appropriate.

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?

Description clearly states the tool extracts text/tables from a blob, with options for async parsing via QStash and callback. It distinguishes from sibling tools like lithtrix_blob_parse_status and lithtrix_blob_download.

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?

Description gives clear context: async=true for QStash, optional callback. However, it does not explicitly state when to use this tool instead of alternatives like lithtrix_blob_search or lithtrix_blob_parse_status, though the purpose is clear enough.

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