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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful data-exposure constraints ('Metadata/approved fields only; no secrets, contacts or original files'), but it does not explain ordering, pagination behavior, or what 'authorised' means in practice.

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 short sentences with no filler. The exposure constraint is front-loaded enough to be useful, though the second sentence is somewhat compressed and could be clearer.

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, three undocumented parameters, and only a minimal description, an agent lacks enough detail to invoke this tool confidently. The description does not explain filtering, pagination, result shape, or how the returned audit events are ordered.

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% and the description says nothing about the three parameters (limit, query, offset). For a tool with three undocumented parameters, the description fails to compensate for the missing schema semantics.

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: 'Read authorised tenant audit events'. That is clear enough for an agent to understand the tool lists audit events, though it does not distinguish the tool from nearby list/get metadata tools such as list_tenant_user_metadata or get_tenant_settings_metadata.

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 'through the existing application' provides almost no actionable context about when this tool should be selected. There is no mention of when to use it versus alternatives, no prerequisites, and no exclusion criteria.

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