fiken_list_journal_entry_attachments

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

No annotations provided. Description only states action without disclosing side effects, error handling, or security requirements. Does not mention that it is read-only or non-destructive, though implied.

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?

Single sentence, directly communicates purpose. No wasted words, appropriate for simple tool.

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?

Lacks description of return format or pagination. No output schema. Does not mention that attachments are file references; minimal context for a tool with no annotations.

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 solid descriptions for both parameters. Tool description adds no additional semantic context beyond what is in the schema.

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 verb 'List' and resource 'attachments for a specific journal entry'. Distinguishes from sibling tools like fiken_list_invoice_attachments by specifying the target entity.

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?

No explicit guidance on when to use this vs other attachment listing tools. Implied by entity type but no alternatives or exclusions mentioned.

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