timeouts

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

Annotations declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so safety profile is partly covered. The description adds useful behavioral context by stating overrides are 'in seconds', but omits whether settings are session-scoped, persistent, or what happens to unlisted timeouts. With annotations present, a 3 fits.

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?

Three compact fragments, front-loaded with the resource and operations. Nothing is wasted, though the telegraphic style leaves little room for the guidance an agent would benefit from.

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?

For a 3-parameter tool with full schema coverage and no output schema, the definition is minimally viable but does not explain what 'get' returns or how the overrides map behaves across sessions. Adequate, with clear gaps in behavioral framing.

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 the schema already documents action, session, and overrides. The description adds the hint that more keys exist beyond connect/reset/memory ('...') and reinforces the seconds unit, but this largely duplicates the schema's own example.

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 resource ('GDB operation timeouts') and two explicit operations ('action=get | set(overrides)'), so an agent knows exactly what this tool manipulates. It does not name or differentiate itself from any sibling, but the resource is distinctive enough to stand apart.

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 gives syntax ('action=get | set(overrides)') but no guidance on when to use this tool, when not to, or what alternatives exist for adjusting debug behavior. An agent must infer the use case entirely.

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