get_trace_log

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

With no annotations provided, the description must convey behavioral traits. It discloses the key requirement (trace must be enabled), but does not describe potential errors, permissions, or whether it is a read-only operation. The mention of the prerequisite is useful, but the description could be more explicit about behavior when trace is not enabled.

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 a single, focused sentence that front-loads the action and resource. It contains no unnecessary words or redundant information, making it highly concise and well-structured.

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 simple getter with one parameter and no output schema, the description provides the essential purpose and a key condition (trace enabled). It is sufficient for an agent to decide when to use the tool, though it could be slightly more complete by mentioning the expected output format or error behavior.

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 input schema already provides full coverage for the single parameter messageId with the description 'The CPI message GUID'. The tool description does not add any additional meaning beyond the schema, so the baseline score 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 the exact function: 'Get step-by-step trace log for a CPI message.' The verb 'Get' and the resource 'trace log for a CPI message' are specific and distinguish this tool from siblings like get_message_details or get_failed_messages.

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 clear usage context by noting the prerequisite: 'only available when trace is enabled on the iFlow.' This tells the agent when the tool can be used, though it does not explicitly mention alternatives or exclusions.

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