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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so the safety profile is covered structurally. The description adds nothing beyond a repeated route string and a pointer to describe_operation; no pagination, aggregation, time-window, or scope behavior is disclosed.

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 same route string is emitted twice, which is pure redundancy, and the only other content is an operation ID hash and a generic pointer. Short, but under-specified rather than concise.

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, 0% parameter documentation, a free-form nested query object, and a namesake sibling in a huge tool set. The description does nothing to bridge any of these gaps, so an agent cannot confidently formulate the query object or predict the response.

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% for two parameters, one of which is a free-form nested object ('query' with additionalProperties) and one an empty 'params' object. The description offers no explanation of what goes in either, leaving the agent with zero guidance on the only real input.

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 tool name as a raw HTTP route ('GET /api/analytics/summary'), twice. It never says in plain language what analytics summary is returned (portfolio? leases? expenses?) or what scope it covers, so an agent cannot distinguish it from siblings like get_redline_analytics_summary or get_dashboard_metrics.

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, or prerequisite guidance. The only hint is 'describe_operation provides native request schemas', which tells the agent how to discover the schema but not when this tool is the right choice over other analytics/dashboard tools.

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