firefly_list_operations

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that the tool lists operations with an optional entity filter, but omits details like whether the list is filtered by permissions, the nature of operations (e.g., predefined or user-specific), or any side effects. The description fails to add behavioral context beyond the basic functionality.

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 with two short sentences. The main purpose is front-loaded in the first sentence, and the parameter description follows logically. No unnecessary words are present; every part earns its place.

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 an output schema (not shown), the description doesn't need to detail return values. The tool is simple with one optional parameter. However, the description lacks details about the entity filter's format and what 'operations' entails, which could leave the agent uncertain about how to use it effectively.

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 description adds some meaning to the single parameter 'entity' by mentioning it as an optional filter with examples ('account, transaction, etc.'). However, schema description coverage is 0%, so the description should compensate more. The examples are vague and lack specificity, leaving interpretation open.

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 the verb 'list' and the resource 'all available Firefly III operations', which directly communicates the tool's function. The optional entity filter adds specificity. The purpose is distinct from sibling tools like firefly_execute (which executes an operation) and firefly_get_schema (which retrieves schemas).

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 provides no guidance on when to use this tool versus alternatives or when not to use it. It doesn't mention prerequisites, exclusions, or comparative context despite having sibling tools that could benefit from such clarification.

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