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

There are no annotations, so the description carries the full burden. It does not disclose read-only behavior (though 'get' implies it), authentication requirements, pagination behavior, or what 'recent' means. The term 'recent' is vague and offers no concrete time frame or ordering 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?

The description is two concise sentences with no redundant words. The core action is front-loaded, and the optional filter is stated clearly. Every word 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?

With no output schema and no behavioral details, the description is incomplete. An agent does not know what the logs contain, how many are returned (though limit default hints), or how they are ordered. It leaves critical return-format information entirely unspecified.

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 description coverage is 0%, so the description must explain the parameters. It mentions 'Optionally filter by automation ID,' which adds meaning for automation_id, but it completely omits the limit parameter and its purpose. The defaults in the schema are not enough context for an agent to use the limit meaningfully.

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 states a clear verb and resource: 'Get recent automation execution logs.' It distinguishes implicitly from siblings like get_automation and list_automations, as no other tool targets logs. However, it does not explicitly name any alternative or scope, so it misses the top score.

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 provided on when to use this tool versus other automation-related tools (e.g., get_automation for configuration, list_automations for definitions). The description only states what it does, with no exclusions or conditional contexts.

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