List Apex Log Limit Risks

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

Annotations already declare readOnlyHint=true and openWorldHint=false, covering the safety profile. The description adds useful behavioral context beyond annotations: results are sorted worst-first and report how much of each limit was used, though it omits pagination, auth, or log-file handling details.

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?

One front-loaded sentence with zero filler. The dash-separated list efficiently enumerates limit types, and the trailing clause covers ordering and usage.

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 two-parameter, read-only analysis tool with fully described schema parameters and annotations covering safety, the description explains what is listed and how it is ordered. It lacks usage guidance relative to sibling tools, but otherwise supplies enough for correct invocation.

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 100%, so both parameters are fully documented in the schema itself. The description's phrase 'nearly consumed' loosely frames the threshold parameter, but adds no syntax, default, or format detail beyond what the schema already provides.

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?

States a specific verb (List) and resource (governor limits an Apex log transaction has nearly consumed), enumerates the limit types, and specifies ordering (worst first) and usage detail. It does not explicitly distinguish itself from sibling tools such as apexlog_list_slow_operations or apexlog_get_summary, so it falls short of a 5.

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 when-to-use, when-not, or alternative-tool guidance is provided. The purpose implies risk analysis of an Apex log, but the agent receives no explicit condition for choosing this tool over get_summary or list_slow_operations.

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