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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and a closed world, so the safety profile is fully covered structurally. The description adds nothing beyond that — no statement about what the returned columns include (names, types, labels) or why entity selection changes the result set.

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?

A single short sentence with no filler, and the verb-resource pair leads. It is arguably too terse for the ambiguity it leaves, but there is zero wasted text.

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?

An output schema exists, so return values need not be described. Still, for a 0%-covered enum parameter in a crowded sibling set, the description should say what 'entity' selects and how this differs from related report tools; it does not.

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 is exactly one parameter, 'entity', with an enum of ten values and a default of 'location'. The description only echoes the word 'entity' without explaining that it selects which report data type's columns are returned, leaving the agent to reverse-engineer the enum values.

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 names a specific verb ('Discover') and resource ('report columns') scoped by entity, which is more than a restatement of the title. However, it does not distinguish this from nearby siblings like get_report, list_reports, or get_report_filter_operators, so an agent must infer the boundary.

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?

Usage is only implied: an agent can deduce this is a discovery/introspection call that precedes building or exporting a report. There is no explicit when-to-use, no mention of alternatives such as preview_report, and no note that this is a prerequisite step.

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