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

With no annotations, the description must carry the full behavioral burden. 'Immutable' usefully signals a read-only, tamper-evident source, but nothing is said about pagination behavior, ordering, time-range coverage, permission requirements, or response shape for a tool with a user-supplied limit.

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?

A single tight sentence with the core noun phrase front-loaded and no filler. It is appropriately sized, though the brevity trades away information the tool needs.

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 2-parameter read tool with no annotations, no output schema, and 0% schema description coverage, the description leaves the agent guessing about required scoping (bot_id), result volume (limit default 50), and what a log entry contains. It is under-specified for the structured-data gaps.

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 neither 'bot_id' nor 'limit' (default 50) is documented anywhere. The description mentions neither parameter and adds no semantics such as whether the logs are scoped to the bot or what limit actually bounds.

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 gives a specific verb ('Get') and resource ('immutable audit logs'), and narrows scope to 'administrative actions and configuration changes', which distinguishes it from nearby log/analytics siblings like get_mailbox_logs. It does not explicitly name an alternative, but the resource is concrete enough to route correctly.

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?

There is no statement of when to use this versus alternatives such as get_mailbox_logs or the analytics tools, and no mention of prerequisites or scoping (e.g., that logs are per-bot). Usage is only loosely implied by the word 'audit'.

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