Get message processing log runs

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

The readOnlyHint annotation already declares the operation as read-only, and the description's 'Get' verb is consistent with that. The description adds the domain detail that a message log entry can have multiple individual processing step runs, but it does not disclose ordering, pagination, or result shape.

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 sentence with no filler. The core object is front-loaded, and the phrasing is compact and precise for a single-parameter read-only getter.

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 read-only resource with one required parameter, the description provides enough to make a correct call: it identifies the resource and the input's role. It omits an explicit output format and usage exclusions, but the readOnlyHint and simple schema keep the gap small.

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 description coverage is 0%, so the description must compensate. 'For a message log entry' gives message_guid its semantic role as the identifier of the log entry whose runs should be fetched, which is meaningful despite the sparse schema.

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 identifies a specific verb and resource: 'Get individual processing step runs for a message log entry.' This distinguishes it from tools like get_message_processing_logs and get_message_processing_log_errors, though it does not explicitly contrast it with the similar get_run_steps sibling.

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 is given for when to use this tool versus related siblings such as get_message_processing_logs or get_run_steps. The intended context must be inferred from the tool name and sibling list rather than stated.

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