Trigger a command

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

Annotations indicate readOnlyHint=false and openWorldHint=true, implying mutation and side effects. Description states 'trigger' but does not explain the action's consequences, limits, or required permissions. Adds little beyond annotations.

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?

Two sentences, front-loaded with core purpose. No redundant words effectively conveys key guidance.

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?

No output schema, but for a trigger tool return might be minimal. Given 4 params and openWorldHint, more context on side effects would improve completeness. Existing guidance on kind and get_settings is adequate but not thorough.

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 description adds meaning for 'kind' (selects list) and 'name' (must match get_settings). For 'hold' and 'extraSettings', description adds no new info beyond 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?

Description uses specific verb 'trigger' and identifies resource 'configured command'. It distinguishes from siblings by focusing on activation of pre-set commands. Includes reference to 'kind' for list selection.

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?

Explicitly directs user to 'Use get_settings to see valid names', providing prerequisite guidance. Does not explicitly state when not to use or mention alternatives, but clearly implies reliance on configured commands.

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