Read Log

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered by structured data. The description adds nothing beyond that: no statement about output shape, size/truncation behavior, whether it parses errors, or failure modes when the path is invalid.

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 zero filler and the resource front-loaded, which is structurally clean. It is arguably under-specified rather than too long, but as pure conciseness it holds up.

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 and one of two parameters undocumented, the description should carry more weight than it does. It omits what a 'summary' contains, how errors in the log are surfaced, and how the required path is resolved, leaving real gaps for a tool whose only job is producing a summary.

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 only 50%: 'log_path' has no description at all, and the description provides no compensating detail about what kind of path it expects (file vs. directory, relative to workspace_root). The optional 'workspace_root' override is explained by the schema, not the description, so the description contributes essentially no parameter semantics.

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?

It names a verb-plus-resource ('Summarize a simulation log'), so the basic action is inferable, but it never says what a simulation log is in this context or how this differs from the many other read_* inspection siblings (read_waveform, read_measures, read_noise, inspect_schematic). The name/description also diverge slightly ('read_log' vs 'summarize'), leaving the exact deliverable ambiguous.

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?

There is no when-to-use guidance, no prerequisite (e.g. must a run have completed first?), and no reference to an alternative tool. The agent must guess from the name alone whether this is for simulator stdout, a batch run log, or a GUI session log.

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