unanet_get_financial_report

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

With no annotations, the description is the only source of behavioral transparency. It only says 'generate and retrieve' without disclosing side effects, whether the report generation is synchronous or asynchronous, required permissions, or data scope. This is insufficient for a tool that likely creates and returns reports.

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, compact sentence with no redundant words. It is front-loaded and easy to parse, though it sacrifices detail for brevity. The conciseness itself is good, but it borders on under-specification.

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 5 parameters (including 2 enums) and no output schema, the description is far too sparse to be complete. It does not explain the variants of financial reports, the meaning of format options, or what the return value looks like. This leaves significant gaps for an agent to select and invoke the tool correctly.

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 input schema covers only 60% of parameters (endDate, projectId, startDate have descriptions, while format and reportType do not). The description adds no parameter-level meaning, such as what report types are available or how format affects the output. The agent must infer parameter semantics solely from the sparse 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?

The description states a clear action ('generate and retrieve') and resource ('financial reports from Unanet'), which is specific enough to understand the basic purpose. However, it does not distinguish this tool from sibling tools like unanet_get_billing_status or unanet_generate_invoice, so it lacks sibling differentiation.

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. It does not mention prerequisites, typical scenarios, or situations where a different tool would be more appropriate. This leaves the agent without contextual cues for tool selection.

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