firefly_get_schema

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

No annotations are provided, so the description carries the full burden. It only says 'Get parameter schema', implying a read operation, but does not disclose behavioral traits such as whether it requires authentication, has rate limits, or any side effects. Minimal information.

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 one line for the purpose and two lines for argument descriptions. It is front-loaded and every sentence adds value without redundancy.

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 simplicity (2 params, no nested objects) and presence of an output schema (not described), the description is adequate but not complete. It does not explain that the output is a schema useful for subsequent calls to firefly_execute, nor does it leverage context from siblings to guide the agent.

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 description coverage is 0%, yet the description adds meaningful explanations for both parameters: 'entity: Entity type (account, transaction, etc.)' and 'operation: Operation name (list, get, etc.)'. This provides context beyond the bare schema titles, though examples could be more exhaustive.

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 'Get parameter schema for a specific operation', specifying the verb ('Get') and resource ('parameter schema'). This distinguishes it from siblings like firefly_execute (executes) and firefly_list_operations (lists operations).

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 tool versus alternatives (e.g., before calling firefly_execute). The description only lists arguments, lacking context like 'Use this to determine required parameters for an operation before executing it.'

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