Get log files

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

Annotations already declare readOnlyHint=true, and the description adds a useful behavioral caveat: '$top not supported server-side; may return 501 depending on tenant.' This warns the agent about a possible failure mode beyond what the annotation conveys.

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 only two sentences, with the purpose front-loaded and a single high-value caveat following. There is no redundant or filler phrasing.

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?

The tool has four undocumented parameters and no output schema, so the description should carry more weight. It covers purpose and one server-side limitation, but leaves parameter syntax, return shape, and pagination behavior completely unexplained.

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 explain the four parameters (skip, filter, select, orderby). It does not explain any of them, and the only query-option note references $top, which is not even in the schema. The agent gets no meaningful parameter guidance.

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 uses a specific verb and resource: 'List runtime log files for troubleshooting iFlow execution.' This is clear and adds context beyond the title, but it does not explicitly differentiate from sibling tools like get_trace_content or get_message_processing_logs.

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 phrase 'for troubleshooting iFlow execution' provides a clear use context. It does not name alternatives or state when not to use this tool, but the intended scenario is reasonably explicit.

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