km_get_trigger_xml

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

No annotations provided; description only states it gets XML and triggers are 1-indexed. Does not disclose read-only nature, error behavior for invalid indices, or permission requirements. With no annotations, burden is on description to provide context, which it fails to do.

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 concise sentences with no wasted words. Directly states purpose and indexing key. Ideal length for such a simple tool.

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?

Tool is simple (no output schema, no nested objects). Description adequately explains purpose but lacks details on return format, error states, or how to know trigger indices. Could be more complete with minimal effort.

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 covers 100% of parameters, each with descriptions ('Macro name or UID', 'Trigger index (1-based)'). Description adds 'Triggers are 1-indexed', which reinforces but does not add new meaning. Baseline of 3 is appropriate.

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 it retrieves the XML definition of a specific trigger in a macro, distinguishing it from siblings like km_set_trigger_xml or km_get_action_xml. The verb 'Get' and the resource 'trigger XML' are specific.

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?

No guidance on when to use this tool vs alternatives (e.g., km_get_action_xml), nor conditions for use (e.g., macro must exist). Only mentions 1-indexed triggers, which is minimal context.

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