get_organization_financial_document

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it does so thoroughly. It reveals that PDF output saves a file to the downloads directory, returns an absolute path, optionally returns base64 content inline, and that JSON output returns parsed content directly. It also states the plan requirements and higher cost for JSON, which are critical behavioral details not visible in the schema.

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 two compact, information-dense sentences. The first sentence states the core operation and resource; the second covers format variations, defaults, plan requirements, side effects, return behavior, and cost with no filler or repetition.

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 tool with no annotations and no output schema, the description explains the return modes, file-saving side effect, inline content option, plan gates, and cost tradeoffs. The only minor omission is guidance on how to obtain the document_id through sibling list tools, but the description still provides enough to invoke the tool correctly for either format.

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?

The schema only describes format and return_base64, leaving id and document_id with bare types, so the description meaningfully compensates by establishing that id identifies the organization and document_id identifies the financial document. It also enriches format and return_base64 with behavior, requirements, and cost implications. The added value is strong but not exhaustive for every parameter edge case.

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 opens with a specific verb and resource: 'Get one financial document for an organization by document id.' The word 'one' and the identifier requirement clearly distinguish this from the sibling list_organization_financial_documents tool, and the format-specific behavior further clarifies what the tool does.

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 gives good context for choosing between format='pdf' and format='json', including plan requirements, cost differences, and output behavior. However, it never explicitly says when to use this tool versus its siblings, such as using list_organization_financial_documents to find document IDs first. The guidance is useful but mainly implied rather than explicit.

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