list_logs

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 the default ordering ('newest first by default'), which is useful context, but says nothing about pagination behavior, total counts, or what 'across bundles' means for scope beyond the schema's bundles parameter.

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 front-loaded sentence with the default sort stated early and no redundant restatement of parameters. Every clause maps to a real capability.

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 all 8 parameters are documented in the schema. The description covers the principal filter dimensions; only pagination/total-count behavior is left unaddressed, a minor gap for a read-only list tool.

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 each of the 8 parameters (start/end ISO semantics, status enum with farmOS 4 caveat, bundles examples, name_contains case-insensitivity) is already documented. The description only summarizes the filter families at a high level, adding little beyond the schema; baseline 3 applies.

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 logs') plus scope ('across bundles') and default ordering. An agent can distinguish it from create_log, set_log_status, and query_records, though the description never names the closest alternative (query_records) 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 implied by the filtering capabilities ('filtered by status, asset, text or date range'), but there is no statement of when to prefer this over query_records or get_record, and no prerequisites or exclusions are given.

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