anon_delete_finance_tx_id

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description adds substantive context beyond them: the required permission scopes, the 403 outcome when deleting another user's entry, and that the project is derived from the API key. This is exactly the auth/error context an agent needs for a destructive mutation.

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?

Front-loads the verb, then permission semantics, then the route; every sentence carries information. Slightly dense with the permission branches but no wasted filler.

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 one-param destructive delete with no output schema, the description covers purpose, authorization, scoping, and failure behavior. It omits return/confirmation semantics, which is minor given the tool's simplicity.

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 0%, so the description carries the burden and does explain that projectId must NOT be supplied (project comes from the API key), adding real meaning about path scope. It gives no format/example for txId itself, so not a 5.

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?

States a specific verb+resource ('删除账目' / delete a finance entry) plus the exact HTTP route DELETE /api/projects/{id}/finance/{txId}. This clearly distinguishes it from siblings like anon_patch_finance_tx_id and anon_get_finance.

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?

Gives concrete authorization rules: needs finance:manage or finance:add, managers can delete any entry, add-level users can only delete their own, others get 403. This effectively defines when the call succeeds. It does not name a sibling alternative (e.g., patch to modify instead of delete), so it stops short of a 5.

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