gateway_knowledge_audit_access

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

The readOnlyHint annotation already covers safety, and the description adds the useful behavioral fact that this tool is a synonym/delegate for another tool rather than a distinct operation. However, it does not describe what the aliased tool actually does, so behavioral transparency remains limited.

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 only six words and easy to scan, but it is under-specified rather than efficiently concise. It contains no functional content, so brevity here comes at the cost of usefulness.

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?

The output schema and readOnlyHint cover return structure and safety, but the description still fails to explain what an access audit is, what the space parameter means, or how this alias behaves relative to the canonical sibling. An agent cannot confidently call it based solely on this definition.

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 has one property, space, with 0% description coverage, and the tool description says nothing about it. The agent is left to guess whether space is an ID, slug, or something else, so the description provides no compensation for the schema gap.

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 clearly identifies the tool as a compatibility alias for gateway_knowledge_access_audit, which tells an agent that this tool exists to mirror the canonical sibling. It differentiates from the many unrelated sibling tools by naming its target, though it does not state the actual operation performed.

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 guidance on when to use this alias versus the canonical gateway_knowledge_access_audit. The word 'compatibility' implies legacy or alternate naming usage, but the description never states a preference, condition, or exclusion.

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