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

The annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds that results include names plus meanings, but it never discloses the three distinct operating modes (search / get / list_namespaces), the 50-item limit, or how deprecated entries are surfaced — behavior an agent would want before choosing an action.

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?

Two tight sentences with no filler: the first defines the resource and its return content, the second states the intended situation. The value proposition is front-loaded and nothing is redundant.

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?

For a six-parameter, multi-mode lookup tool with no output schema, the description covers what is returned but omits the mode structure entirely — an agent cannot tell from the text that `query` belongs to search and `names` belongs to get. It is adequate for a simple lookup but leaves the most consequential behavioral detail to the enum values alone.

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 a moderate 67%, and the description adds essentially no parameter meaning beyond it. Most critically, the required `action` enum has no explanation anywhere in text — the description never tells the agent that search, get, and list_namespaces are three different operations with different required companions (query vs. names).

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?

"Look up the OpenTelemetry semantic conventions: the standard names of attributes and metrics, with their meanings" names a specific verb and resource and even states what the results contain. It does not explicitly differentiate itself from the adjacent get_instrumentation_guide sibling, which an agent could plausibly confuse it with, so it falls short of a 5.

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?

"For choosing names when adding instrumentation" gives an implied usage context, which is more than nothing, but there is no when-not guidance and no mention of alternatives such as get_instrumentation_guide or get_schema. The agent must infer that this is a pre-instrumentation naming reference rather than a lookup for existing telemetry.

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