anon_get_finance_export

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

The annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds substantial context beyond them: the required finance:manage permission, the exact filter semantics for the target member, the response media type, UTF-8 BOM, Content-Disposition: attachment, and the full column list. It also clarifies that projectId must not be passed because the project derives from the API key — a non-obvious constraint.

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?

It is dense but front-loaded, opening with the action and permission, then filter semantics, then response format. The column enumeration is long but pays for itself by telling the caller what the CSV will contain. No sentence is pure filler, though the endpoint/URL restatement is slightly redundant.

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?

With no output schema, the description compensates fully by specifying the response content type, encoding, disposition header, and exact columns. Permission needs, scoping rules, and the auto-derived project are all covered, so nothing an agent needs to call this correctly is 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?

There is a single userId parameter whose schema description covers its default and membership requirement, but the tool description adds the crucial behavioral meaning of that parameter — it selects the member whose related ledger entries are exported (as payer or split participant). That is real semantic value beyond the schema's field-level text.

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 states a specific verb (导出/export) and resource (账目 CSV / finance ledger), and its scope ('导出目标成员相关账目') clearly distinguishes it from the sibling anon_get_finance, which is the non-export listing endpoint. An agent can identify the tool's job without opening the schema.

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?

It gives concrete preconditions (需 finance:manage 权限) and defines exactly which entries are exported (payer, empty splitAmong, or member in splitAmong) plus the sort order, so the agent knows the situation this tool fits. It stops short of naming when to prefer it over anon_get_finance (JSON list vs CSV download), so it isn't a full when/when-not statement.

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