list_organization_financial_documents

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It does add useful context: the operation is a read-only listing, and Premium+ access is required. However, it does not mention pagination, period formatting, or error conditions, and with zero annotation coverage some behavioral transparency is still missing.

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 a single, efficient sentence with no filler. The action, object, scope, and access requirement are all packed in without redundancy, and the most important information is front-loaded.

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 with only one parameter and has an output schema, so the return structure does not need to be described. The description covers what is listed and the plan requirement, and the parameter meaning is reasonably inferable. It lacks an explicit alternative pointer and detailed id format, but those are secondary for such a simple list tool.

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 input schema only defines an unannotated 'id' string, and schema description coverage is 0%. The phrase 'for an organization' gives the key semantic cue that id is the organization identifier, which is helpful. However, it does not specify whether the id is the KRS number, an internal ID, or how to obtain it, leaving some ambiguity.

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 clearly states the action ('List') and the resource ('financial document groups by accounting period') plus the data source ('KRS') and scope ('for an organization'). This clearly distinguishes it from the sibling get_organization_financial_document, which fetches a single document rather than listing groups.

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 useful context: the tool enumerates document groups and requires a Premium+ plan, which helps an agent decide when it is applicable. It does not explicitly name alternatives or say 'use get_organization_financial_document for a specific document,' but the plural 'groups' strongly implies the enumeration role.

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