get_trigger_source

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

The description discloses that the tool returns raw PSQL text or an error message if not found, implying a read-only operation. Since no annotations are provided, the description carries the full burden and adequately conveys the expected behavior without contradictions.

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 concise, consisting of two short sentences that front-load the core purpose and return value. Every sentence adds value with no extraneous text.

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?

Given the tool's simplicity (2 parameters, no output schema), the description is largely complete. It covers the purpose and return format, but could mention that it complements 'list_triggers' or that the source is read-only.

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?

Description coverage is 100% in the schema, so the baseline is 3. The description does not add any additional meaning to the parameters beyond what the schema already provides, such as the formatting note for 'trigger'.

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 tool's purpose: returning the full PSQL source body of a trigger. The verb 'Return' and resource 'PSQL source body of a trigger' are specific, and it distinguishes from sibling tools like 'get_procedure_source' or 'get_view_source'.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, when not to use it, or how it compares to sibling tools like 'describe_table' or 'list_triggers'.

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