scan_log

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

Discloses tier-based bounds on results (unbounded for Pro, last 100 for Free), which is a key behavioral trait. However, lacks details on result ordering, time range, side effects, or authentication needs.

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?

Extremely concise—two sentences front-loaded with purpose. Could add more detail without losing conciseness, but current form is efficient.

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 has 4 parameters and an output schema, the description is too sparse. It omits how to use risk_filter, the meaning of limit, and what the output contains. Incomplete for effective use.

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?

With 0% schema description coverage, the description should explain parameters. It does not mention tenant_id, risk_filter, limit, or api_key, leaving their roles entirely implicit.

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 it returns recent scan logs and distinguishes between tier limits. However, it lacks an explicit verb like 'retrieve' or 'list', but the purpose is clear.

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?

No guidance on when to use this tool versus alternatives. The tier limitation is noted but does not help in decision-making among siblings like list_rules or scan_prompt.

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