create_log_adjustment

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

With no annotations, the description must carry the full burden. It states 'temporarily adjust' implying the change is not permanent, but does not disclose what happens when the duration expires, whether authorization is needed, or that it creates an entity (as suggested by the sibling delete_log_adjustment).

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 a single, concise sentence that conveys the core purpose without unnecessary words.

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?

The tool creates a temporary adjustment but no output schema is provided. The description does not mention return values, side effects, or what happens if a duplicate adjustment is created. Given the moderate complexity, more detail is needed for completeness.

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%, so the description should compensate. It mentions 'log level' and 'logger namespace' but omits the required duration_ms parameter. The description adds limited value over the schema.

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 clearly states the action ('adjust'), the resource ('log level for a specific logger namespace'), and the temporary nature. It distinguishes from siblings like delete_log_adjustment (delete) and list_log_presets (list).

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?

The description indicates temporary use but does not explicitly state when to use this tool versus alternatives (e.g., for permanent changes, or to view current logs). No exclusions or alternative tools are mentioned.

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