finance_equity_research_macro_synthesis

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

With no annotations, the description should disclose behavioral traits, but it only mentions internal routing (JWT, tenant, company scope). It does not describe side effects, idempotency, permissions, or output behavior. The output schema exists but is not elaborated.

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 short but includes unnecessary infrastructure details (routing through dispatcher) that are irrelevant for tool selection. The structure is acceptable but could be more focused on purpose.

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 complexity of a domain agent action with two parameters, the description is severely incomplete. It fails to explain the core function, expected input formats, or output structure, leaving the agent without sufficient context to use 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?

Schema coverage is 0%, so the description must compensate. It adds minimal value by describing 'message' as 'Free-text objective' and 'inputs' as 'Optional JSON string', but these are vague and lack constraints, examples, or format guidance. The agent cannot infer valid inputs.

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 merely restates the tool name as 'Run the finance domain agent action equity_research_macro_synthesis' without explaining what the action does. It lacks a specific verb and resource, and does not differentiate the tool from siblings like finance_dcf_lbo_spreadsheet or finance_peer_valuation_multiples.

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 guidance is provided on when to use this tool versus alternatives, what prerequisites exist, or how to differentiate between using free-text message versus structured inputs. The agent is left without context for appropriate invocation.

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