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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and closed-world, so the safety profile is covered. The description adds nothing beyond that — no indication of filtering behavior, pagination, aggregation semantics, or data freshness for this analytics read.

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?

Short, but the space is spent on a duplicated URL string and an operation ID rather than a front-loaded purpose statement. Brevity here reflects 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?

A parameterized analytics endpoint with a nested free-form query object, no output schema, and no documented parameters needs the description to explain what is returned and how to filter; none of that is present, so an agent cannot invoke it correctly without falling back to describe_operation.

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 description supplies no parameter meaning at all. The two parameters (a free-form 'query' object with arbitrary properties and an empty 'params' object) remain completely opaque — an agent cannot know what query keys are accepted.

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 is the URL path for /api/redline-analytics/high-risk-contracts repeated verbatim, which is essentially a restatement of the name and title rather than an explanation. 'High-risk-contracts' hints at the resource, but there is no verb or statement of what is computed/returned, and nothing distinguishes it from siblings like get_redline_analytics_risk_dashboard or get_redline_analytics_kpis.

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?

No when-to-use, when-not-to-use, or sibling comparison is given. The only actionable hint is 'describe_operation provides native request schemas', which routes the agent to another tool for schema discovery but says nothing about when this endpoint is the right choice.

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