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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered structurally. The description adds nothing beyond that — no indication of what the summary aggregates, whether it is scoped to a portfolio or the current user, or how expensive the call is.

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 content is a duplicated endpoint string rather than front-loaded meaning. Brevity here comes from under-specification, not efficiency.

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, no parameter documentation, and an untyped free-form query object — the description should carry the burden of explaining accepted filters and the shape of the summary, and it provides none of that.

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?

Two parameters (query, params) with 0% schema description coverage and the description says nothing about either. An agent cannot tell which filter keys are accepted in the free-form 'query' object or why 'params' 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 text repeats the raw endpoint path twice plus an operation ID; it never states in plain language what a 'portfolio reassessments summary' contains (counts, aggregates, per-lease rows). The name/title already conveys the same path, so this is effectively tautological.

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 only routing hint is that describe_operation exposes native request schemas, which is a pointer for schema discovery rather than when-to-use guidance. It does not distinguish this from siblings such as get_portfolio_reassessments_materiality_e65ee814a4ade95673dc61a8, get_lease_reassessments_869e75f386f3a30488016b42, or get_reassessments_pending_543634d03377f7b8399b1d63.

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