finance_corporate_issuers_review

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

With no annotations, the description carries the full burden. It mentions routing via the domain-agent dispatcher with JWT/tenant/company scope but omits critical details like side effects, return behavior, or async nature.

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 (4 lines) and front-loaded with the action name. No redundant information, but it is under-specified for a tool with no other documentation.

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?

For a tool that likely performs a specific finance review, the description lacks detail on what it does, what inputs it expects, and what outputs it returns. An output schema exists but its content is not described.

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?

Despite 0% schema coverage, the description adds basic meaning: message is a 'Free-text objective' and inputs is an 'Optional JSON string'. However, no further constraints or examples are provided, limiting utility.

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 it runs a domain agent action with the specific name 'finance_corporate_issuers_review', but does not elaborate on what that action does, leaving the purpose vague. Among many finance siblings, it lacks 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?

No guidance on when to use this tool versus alternatives like finance_chat or other specific finance actions. It provides no context for selection.

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