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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety behavior is covered by structured data. The only added behavioral information is the pointer to describe_operation for native request schemas, which is mildly useful for discovery but discloses nothing about scope, filters, or result shape.

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 first sentence is a verbatim duplicate of the path in the title, repeated twice back to back, which is pure waste. The one informative clause (describe_operation pointer) is buried at the end after the redundancy.

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?

A two-parameter, nested-object tool with no output schema and zero parameter documentation needs its description to carry the burden, and this one does not. The only real information is the redirect to describe_operation, which pushes the essential detail out of band rather than completing the definition.

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 (an unconstrained 'query' object and an empty 'params' object) are entirely opaque. The description does not compensate at all beyond noting that describe_operation provides native request schemas, leaving the agent to make a separate call to learn what can be passed.

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 raw endpoint path twice; it never states in prose what a 'contract-period-overview' of expenses returns or how it differs from the very similar sibling get_expenses_contract_period_by_contrac... or get_expenses_period_overview. An agent can infer a read of expense data grouped by contract period, but that is inference from the path, not an articulated purpose.

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, no mention of prerequisites, and none of the many near-duplicate expense and contract-period siblings are named as alternatives. Nothing tells an agent why it would pick this over get_expenses_period_overview or get_expenses_contract_expense_dashboard.

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