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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is fully covered elsewhere. The description adds nothing about aggregation semantics, scoping, pagination, or volume for an entity-level rollup endpoint.

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 first two sentences are verbatim duplicates of the same endpoint path, which is pure waste. What remains is a pointer sentence; brevity here reflects under-specification rather than efficient communication.

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 nested-parameter endpoint with no output schema and no parameter documentation, an agent cannot tell what entities are returned, what query supports, or how to shape the request. The description leaves nearly all of that to a follow-up call.

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% and both parameters (query as a free-form nested object, empty params object) are undocumented. The description does not explain what query filters are valid or give examples; it only defers to describe_operation, which is a pointer rather than semantic content.

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 repeats the HTTP path already present in the title and operation ID; it never says what a 'portfolio rollup entity' is or what the call returns. It is effectively a tautology of the name, distinguishing it from siblings like get_portfolio_rollups_metrics or get_portfolio_rollups_snapshots not at all.

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 statement of when to use this versus the many sibling portfolio/dashboard tools. The only actionable hint is that describe_operation exposes native request schemas, which is a how-to-discover-params note, not usage guidance.

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