List assets in a Money Forward ME manual account

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the agent knows it's a safe read operation. The description adds no additional behavioral context (e.g., error handling, rate limits), but it is consistent with annotations.

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 sentence plus a directive, conveying all necessary information without any wasted words. It is concise and 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 description, combined with annotations and output schema, is mostly complete. It covers usage, parameter, and safety. Minor omission: no mention of behavior for invalid IDs or empty results, but these are likely covered by error handling.

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 100% with a description for the only parameter. The description reinforces that the ID should be passed exactly, but adds no new meaning beyond the schema's 'Opaque id returned by money_forward_list_manual_accounts'.

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 'Lists assets for one custom/manual account.' It uses the verb 'lists' with a specific resource 'assets' and scope 'for one custom/manual account', distinguishing it from siblings like 'money_forward_list_manual_accounts' which lists accounts.

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 explicitly provides a prerequisite: 'First call money_forward_list_manual_accounts and pass its id exactly.' This tells the agent exactly when and how to use the tool, offering clear sequential guidance.

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