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

Annotations only cover readOnlyHint=true, so the description carries real weight and delivers: warning-first sorting, newest-first within type, a 200-character message cut with a message_truncated flag, and the response envelope (total, returned, truncated, scope). It does not state pagination limits beyond the schema's default limit of 50, but the ordering and truncation disclosures are genuinely additive for a read-only tool.

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?

Front-loaded with the verb and resource, then moves to the scope constraint, then to the response fields. Dense but each sentence carries distinct information; the sorting and truncation clauses could arguably be tightened but they are not filler.

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?

With no output schema, the description must describe return values, and it does: it enumerates the row fields, the sort order, the truncation behavior, and the envelope fields (total, returned, truncated, scope). Combined with 100% schema coverage on the six parameters, an agent has everything needed to call this correctly.

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 100%, so the schema already documents every parameter including the scope_required refusal rule for all_namespaces. The description largely restates the scope requirement and instead spends its words on response shape, so it adds little parameter-level meaning beyond the structured fields. Baseline 3 is appropriate here.

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?

Opens with a specific verb+resource ('Fetch Kubernetes events') and immediately enumerates the row contents (type, reason, message, involved object, count, timestamps), which separates it from generic resource listers like get_pods or get_deployments. The closing sentence names the diagnostic scenario (why pods fail, deployments stall), giving an agent a concrete reason to pick this tool over sibling listers.

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?

States the precondition clearly: 'A list needs namespace, an involved_object_name, or all_namespaces=true', which is exactly the gating rule an agent must satisfy. It stops short of naming alternatives or when-not-to-use (e.g., versus get_pod_logs or resource_timeline for deeper diagnosis), so it gives context but no exclusion guidance.

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