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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds nothing beyond a pointer to describe_operation: no mention of scope, filtering, pagination, or what a 'snapshot' record represents.

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 endpoint path is literally repeated verbatim, which is pure waste, and the operation ID adds nothing for an agent. The one genuinely useful sentence (describe_operation provides native schemas) is buried last.

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?

No output schema, a nested free-form query object, zero schema coverage, and dozens of adjacent portfolio-rollups tools. For this complexity level the description should at minimum say what the snapshots list contains and how to filter it; it does neither.

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 there are two parameters, one a free-form 'query' object with additionalProperties and no documented keys. The description gives no parameter meaning at all and only redirects to describe_operation, which leaves an agent unable to construct a useful request without a second call.

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 simply restates the endpoint path 'GET /api/portfolio-rollups/snapshots' twice, which is a tautology of the tool name. There is no verb or explanation of what a 'snapshot' is or how this differs from close siblings such as get_portfolio_rollups_history, get_portfolio_rollups_metrics and get_portfolio_rollups_entities.

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 statement of when to use this tool versus the many other portfolio-rollups endpoints. The only actionable guidance is a meta-hint to call describe_operation for native request schemas, which is procedural rather than selection guidance.

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