finance_portfolio_monitoring

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

No annotations are present, so the description carries the full burden. It mentions routing under JWT/tenant/company scope, but does not disclose side effects, data sources, or what the action actually does beyond the routing mechanism. This is insufficient for a tool with no annotations.

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 relatively short and includes an Args section, but the inclusion of technical routing details ('Routes through the platform's domain-agent dispatcher under your JWT, tenant, and company scope') is not essential for the agent's understanding of the tool's purpose. The information could be more concise and focused on the tool's functionality.

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 two optional parameters, an output schema, and no annotations, the description is inadequate. It does not mention what the tool returns, what kinds of actions it performs, or how it fits into the portfolio monitoring workflow. The agent lacks sufficient context to use the tool 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?

Schema description coverage is 0%, so the description must compensate. It defines 'message' as 'Free-text objective' and 'inputs' as 'Optional JSON string', which adds minimal meaning. It does not specify valid formats, examples, or what types of inputs are accepted, leaving the agent with little guidance beyond parameter names.

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 the finance domain agent action for portfolio monitoring, which gives a general purpose. However, it lacks a specific verb and resource (e.g., 'fetch portfolio performance metrics') and does not differentiate from sibling finance tools like finance_risk_monitoring or finance_chat.

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. The description only explains the technical routing, without stating appropriate contexts or exclusions.

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