audit_audit_get

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

With no annotations, the description must disclose behavioral traits. It only states a read operation ('retrieve'), omitting details like what happens if the ID is invalid, permission requirements, or rate limits. The lack of such information leaves the agent uncertain about side effects or error conditions.

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 a single, front-loaded sentence with no wasted words. It efficiently conveys the core purpose without extraneous information.

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?

Given the tool's simplicity (one parameter, output schema provided), the description is minimally adequate. However, it could be more complete by noting that it returns a single event object matching the ID, or by referencing the output schema. The presence of many sibling tools suggests additional context would help selection.

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 0%, so the description should explain the event_id parameter beyond the schema. It adds no additional meaning—it repeats 'by ID' but does not specify the format or expected value. The agent relies solely on the schema, which only defines it as a required string.

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 states the action ('retrieve'), the resource ('event'), and the method ('by ID'). It distinguishes from siblings like audit_audit_search (which returns multiple events) and audit_audit_clear (which performs a different operation).

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 implies usage when you have a specific event ID, but it does not explicitly state when to use this tool versus alternatives like audit_audit_search for unknown IDs or audit_audit_export for bulk operations. No exclusion or context about prerequisite steps is provided.

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