Parse log line

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

Goes well beyond the annotations by disclosing the 4 KB limit, the no-guessing failure mode (recognised=false), and a trust boundary warning that field values are untrusted log data — a genuinely useful safety cue for downstream handling. Annotations already cover read-only/idempotent/non-destructive, and nothing here conflicts with them.

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?

Four compact sentences, front-loaded with the core action and limit, then formats, then failure behavior, then the trust caveat. No filler sentences.

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 carries the return burden and does disclose the recognised=false flag plus that values are raw log-derived. It doesn't enumerate the structured field set, but for a two-parameter parser this is close to complete.

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 the baseline is 3; the description adds value by naming the concrete formats the 'format' enum selects between and by marking auto-detection as the default path. It stops short of describing per-format constraints, but the schema already handles those.

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 ('Parse one log line/event into structured fields') and immediately scopes the supported input families (Sysmon JSON, syslog/auth.log, Windows event text). An agent can tell exactly what this does and what inputs it accepts without opening the schema.

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?

Gives clear context: one line at a time, max 4 KB, multiple formats, and the fallback behavior when input is unrecognised. It does not name when-not-to-use or an alternative tool, but no sibling overlaps this parse function, so the omission is minor.

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