provider_query_audit_trail

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond restating the HTTP endpoint: no mention of pagination semantics, default result ordering, time-scope of the audit trail, or permissions required. Since openWorldHint=true and this is a cross-system audit surface, some scoping context would add real value.

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?

It is short and front-loaded with the operation, but the second line is a raw URL that adds little semantic information an agent can act on. It is tersely structured rather than genuinely efficient, with almost no substance to be concise about.

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 a fully described 5-param schema, complete annotations, and no output schema, the core requirements to call the tool are met. The gaps are what the returned audit events represent and any default time-window or ordering behavior, which an agent would need for correct interpretation.

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 coverage is 100%, so page, pageSize, filter (FIQL), sortAsc, and sortDesc are already fully documented in the schema. The description adds no extra meaning (e.g., FIQL syntax example or typical sortable fields), so baseline 3 is correct.

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+resource ("Get list of audit trail events") and adds the underlying endpoint, which is enough for an agent to know this retrieves audit trail records. It does not, however, distinguish the tool from any sibling (e.g., eventbroker_get_audit_log_filter_entry_by_id or eventbroker_get_events), so the ceiling of 4 applies.

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?

"Get list of audit trail events" gives no when-to-use context, no exclusions, and no named alternative among a very large sibling set that includes other audit/event log tools. The agent must infer usage entirely.

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