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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered elsewhere. The description adds only a pointer to describe_operation; it says nothing about filtering, aggregation, pagination, or what the rollforward actually covers beyond the 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?

Very short, but the first sentence is duplicated verbatim, which is waste rather than economy. Nothing is front-loaded about purpose or usage; only the schema-pointer sentence carries information.

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?

With no output schema, an untyped free-form query parameter and 0% schema coverage, the description leaves the agent unable to construct a correct call without first invoking describe_operation. The nested/opaque parameter shape plus the dense sibling set demands far more context than this provides.

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 additionalProperties bag and an empty 'params' object) are opaque, so the description must compensate and does not. No mention of which query keys are meaningful, date ranges, entity scoping, or why 'params' exists and is empty.

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 endpoint path twice ('GET /api/portfolio-matrix/rollforward'), which restates the title rather than explaining what a rollforward is or what it returns. It does convey a read operation on a portfolio-matrix rollforward resource, but gives no notion of scope or content, and offers nothing to distinguish it from get_portfolio_matrix_38a8614a3c0a69d282e82f75 or the get_portfolio_rollups_* siblings.

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 when-to-use or when-not-to-use guidance. The one actionable pointer — 'describe_operation provides native request schemas' — tells the agent how to learn the contract, but not when this endpoint is the right one versus the many portfolio/rollup siblings.

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