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 fully covered. The description adds no behavioral context beyond that: no note on whether results are paginated, whether the response is a portfolio-level rollup versus per-lease rows, or whether write/auth scope matters.

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 string is duplicated verbatim, which is pure waste. The remaining sentence is a boilerplate operation-ID line. There is no front-loaded explanation of purpose, so the few tokens present are not earning their place.

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 tool has nested/free-form input, no output schema, and no parameter documentation anywhere, so the description should explain the response shape and the accepted query filters. Neither is covered. The only compensating element is the redirect to describe_operation for the native request schema.

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 free-form parameters ('query' accepting arbitrary keys and an empty 'params' object), so the description carries the burden of explaining what filters are accepted. It says nothing, offering only the generic pointer to describe_operation. That pointer is mildly useful but does not explain the query surface.

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 is the endpoint path repeated twice: 'GET /api/portfolio-reassessments/materiality'. It names a resource and HTTP verb, but at the level of the name/title rather than explaining in prose what the tool returns (materiality thresholds? reassessment materiality determinations for the portfolio?). It does not distinguish itself from nearby siblings such as get_portfolio_reassessments_summary or get_reassessments_by_id.

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 get_portfolio_reassessments_summary or get_lease_reassessments. The only routing value is the note that 'describe_operation provides native request schemas', which points at an alternative tool for schema discovery but says nothing about task selection.

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