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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds meaningful behavioral context: what fields each mode returns, that variables like $service must be passed in `variables` for chart runs, and what templates mode computes (compatibility score with recommended/missing fields). Not exhaustive on pagination/size limits, but well above the annotation baseline.

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-loads the base case then the two modes, all in two dense sentences. Every clause carries information, though the second sentence is long and requires careful parsing.

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, so the description competently describes return shapes for each mode. Covers the key cross-tool linkage (variables handoff to run_log_chart, template creation path). Missing only edge behavior like pagination and empty-project handling.

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 coverage is 100%, so parameters are already documented; the description nonetheless explains the semantic effect of each parameter (uuid -> detail form, templates:true -> template list with fit scoring) and notes the live coupling to run_log_chart's variables. Adds meaning beyond schema for a baseline-3 100%-coverage case.

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?

States a specific verb and resource (list log dashboards) and precisely enumerates what's returned (name, tags, widget count, template, last update). It also names sibling tools it routes to (run_log_chart, create_log_dashboard_from_template), making it clearly distinguishable.

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?

Explicit conditional usage: without uuid -> list summary; with uuid -> detail; with templates:true -> also templates with compatibility. Names the alternative tool for each follow-on action. Nothing is left to inference.

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