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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that — no scoping, pagination, filtering, or data-freshness context — and merely repeats the endpoint string.

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?

It is short, but the first two sentences are an exact duplicate of the tool title, which wastes the only front-loaded position. The only useful content, the describe_operation pointer, is buried after the repetition.

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, 0% parameter documentation, an empty `params` object, and a very large sibling set of similarly named portfolio tools, the description leaves the agent unable to determine what the tool returns or how to invoke it correctly. It should at minimum explain the matrix contents and how to specify the query.

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 the two parameters (query, params) are opaque: `query` is an unconstrained object of arbitrary properties and `params` accepts nothing at all. The description provides zero parameter meaning, leaving the agent with no way to know what to pass.

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 HTTP method and path ("GET /api/portfolio-matrix") twice, which is a tautology of the name/title. It never says what a portfolio matrix is, what data it returns, or how it differs from the many portfolio siblings (get_portfolio_rollups_metrics, get_portfolio_matrix_rollforward, view_portfolio_dashboard).

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?

The single actionable sentence points to describe_operation for native request schemas, which is a schema-retrieval hint rather than guidance on when to call this tool versus alternatives like get_portfolio_matrix_rollforward or view_portfolio_dashboard. No conditions, exclusions, or prerequisites are stated.

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