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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds an authorization constraint (owner/admin only) that annotations cannot express, which is exactly the kind of extra context the rubric credits. It stops short of describing pagination semantics or result ordering.

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?

Two short sentences, purpose front-loaded before the access caveat — an appropriate size for the tool. The 'Please note that' framing is slightly padded but nothing is redundant.

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?

An output schema exists, so return values needn't be explained, and the required access role is stated. Still missing for a 5-parameter filtered read tool: default behavior when date_range or activity_type is omitted, and how page_number/page_size interact — gaps the schema alone doesn't fully close.

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 description mentions no parameters at all. With schema description coverage at 60%, page_size and the date_range object lack descriptions and the description does not compensate, leaving the agent dependent on schema inference for filtering and paging behavior.

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 and resource ('Get audit logs for the user activity in your organisation'), so an agent immediately knows what it retrieves. No sibling tool in the list covers audit logs, so differentiating isn't strictly needed, but the description adds no explicit scoping (time span, org scope) beyond the generic statement.

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 description gives one concrete prerequisite — only `owner` and `admin` role users can access the endpoint — which is genuinely useful gating information. However, it offers no guidance on when to prefer this over related tools (e.g., analytics or webhook_history) or how the optional filters should be combined.

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