get_session_trigger_context

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds the conditional result has_trigger=false for sessions not originating from a trigger, which is useful behavioral detail beyond the annotations and does not contradict them.

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 short sentences with no filler. The core verb, resource, and conditional return behavior are all front-loaded, and each clause earns its place.

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?

Even without an output schema, the description conveys the main return values: trigger, execution, and has_trigger flag. It does not specify error handling for invalid or missing session_id, but that is a minor gap for a simple read-only lookup.

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?

The schema's session_id description is circular ('session_id da sessão'), so the description adds meaning by explaining that this parameter is the starting point for tracing back to the originating trigger and execution. It doesn't add format or constraints, but for a single string identifier that is acceptable.

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?

Clear verb+resource: it returns the trigger and originating execution for a given session_id, plus a has_trigger flag. It is not explicitly contrasted with sibling tools, but the reverse-navigation wording makes its unique purpose identifiable.

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?

Usage context is implied ('a partir de um session_id', reverse navigation), so an agent can infer when to call it. It does not name alternatives or state when not to use it, so guidance is contextual rather than explicit.

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