seerr_list_settings_logs

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

The readOnlyHint annotation already signals a safe read operation. The description adds no behavioral traits beyond stating that it returns logs—no mention of filtering, pagination, log levels, or other side effects. It adds minimal value beyond the annotation.

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?

The description is extremely short—two words—which is under-specification rather than genuine conciseness. It lacks essential details, making it too terse to be considered well-structured.

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?

Despite having an output schema, the tool has four parameters and no guidance, and the description is overly minimal. It doesn't explain the nature of the logs, the parameter semantics, or any usage context, leaving the agent with insufficient information to invoke the tool correctly.

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?

The input schema has four parameters (skip, take, filter, search) with 0% description coverage. The description 'Returns logs' provides no explanation of these parameters, what the 'filter' default 'debug' means, or how they affect the results. The description fails to compensate for the schema's lack of parameter documentation.

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 'Returns logs' uses a verb and resource, but it's vague about what kind of logs and how this tool differs from the many other settings/list sibling tools. It's not a tautology, but it lacks the specificity needed to clearly distinguish 'settings_logs' from other list operations.

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 guidance on when to use this tool versus other list or settings tools, no context about prerequisites, and no mention of alternatives. The description simply states what it returns without any usage direction.

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