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

Annotations already establish readOnly=true, destructive=false, and non-open-world, so safety is covered. The description adds real value beyond them by disclosing the bounded scope and the significant limitation that raw log samples are not returned, preventing a false expectation about data volume.

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 zero filler, and the positive scope statement is front-loaded ahead of the exclusion. Every clause earns its place.

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 explained, and annotations carry the safety profile. The description covers scope plus the key limitation, leaving only minor gaps like what a 'saved focus window' represents.

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 the single parameter, so the description must carry weight. It conveys that logId identifies one accessible log (an access-scoped constraint) but gives no format or sourcing detail, leaving the parameter only partially characterized.

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 (Read) and precisely enumerates the resource contents: bounded metadata, channel schema summary, and saved focus window for one log. It clearly implies single-log retrieval by id, distinguishing it from list_logs, but never names that sibling explicitly.

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: 'for one accessible TuneWorks log' signals a per-log lookup, typically after listing. The negative scope note ('Raw log samples are not returned') hints at when not to use it, but there is no explicit when-to-use guidance or named alternative.

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