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

No annotations are provided, so the description carries the full burden of behavioral disclosure, but it says nothing about side effects, runtime, read-only versus mutating behavior, or required credentials. The external catalog link is a pointer, not a disclosure of tool behavior.

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?

At roughly fifteen words, it is short, but every word is filler: one sentence repeats the tool name and the other points to a URL. This is under-specification rather than effective conciseness.

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?

The description omits purpose, inputs, outputs, and behavior. With no annotations, no output schema, and no parameter definitions, this is far too sparse for an agent to invoke the tool correctly, especially given the large set of run_* siblings.

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?

There are zero named parameters, and the schema only allows arbitrary additional properties, so there is little for the description to add. This meets the zero-param baseline of 4, even though the description offers no hints about what an arbitrary payload might contain.

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 only restates the tool name ('MCP-Agents tool run_portfolio_analytics') and points to a catalog URL; it never states what action is performed or what result is produced. This is a tautology plus a link, so an agent cannot distinguish it from run_quantitative_analysis or fetch_portfolio_metrics.

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?

There is no guidance about when to use this tool versus the many similar run_* siblings, nor any prerequisites or contextual trigger. The only usage signal is the name 'run_portfolio_analytics', which forces the agent to infer intent rather than receiving explicit direction.

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