get_lords_business_document

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

With no annotations, the description establishes that this is a read/download-style operation and gives unusually useful return behavior: the document record, and for PDFs a descriptor with binary, contentType, sizeBytes, and downloadUrl, including the need to fetch downloadUrl for the file. It does not discuss auth, rate limits, or error cases, but the core behavior is well disclosed.

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 front-loaded and structured with clear Args and Returns sections. It contains some redundancy between the opening summary and the Returns section, and the pipe-separated phrasing is a little fragmented, but it remains efficient.

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 simple one-parameter getter with an output schema, the description is complete: it explains the id source, the list-before-get workflow, and the key return shape, including the PDF download follow-up. Nothing essential for correct invocation appears to be missing.

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 meaning. It does this by explaining that document_day_id is a DocumentForDayId obtained from get_lords_business_documents_for_date, which is the key semantic context beyond the bare integer schema.

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 gives a specific verb and resource: get a Lords business document for a day, and elaborates that it is a business paper/document fetched by id. It also distinguishes the tool from its closest sibling by explaining that it should be used after get_lords_business_documents_for_date.

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 description explicitly states when to use this tool: after get_lords_business_documents_for_date, to fetch one document. It names the sibling tool and makes the list-then-fetch workflow clear, leaving little to inference.

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