Konten auflisten

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

No annotations are provided, so the description carries the burden. It does disclose the unlock requirement as a prerequisite, which is useful operational context. However, it doesn't clarify the read-only nature explicitly or what the exact output format/return value looks like beyond mentioning 'plist', leaving some behavioral ambiguity.

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 extremely concise at three short sentences, front-loaded with the primary action. Every sentence earns its place: what it does, why it's useful, and a key prerequisite. Zero waste.

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?

Given the tool has zero parameters, no output schema, and a single sibling tool, the description covers the essential context well. It explains the relationship to export_transactions (which is the main contextual gap a user faces) and the unlock prerequisite. Minor gap: no mention of output format details beyond 'plist', but this is minor for a parameterless listing 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 tool has 0 parameters, so the description doesn't need to explain parameter semantics. The baseline of 4 for zero-parameter tools applies here, as there's nothing to compensate for. The description efficiently communicates all the relevant meaning for a parameterless tool.

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 is specific and clear: it exports the account list from MoneyMoney as a plist file. It explicitly states the purpose is to reveal exact account names for use with the account parameter of the sibling tool export_transactions, which strongly distinguishes it from that sibling.

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 states a clear prerequisite ('MoneyMoney muss entsperrt sein' / MoneyMoney must be unlocked) and its usage context (to get exact account names for export_transactions). It doesn't explicitly state when NOT to use it, but the context of revealing exact account names makes the use case clear given the sibling relationship.

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