list_log_entries

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds the default time range and return type, but the output schema covers return values. Additional behavioral context (e.g., rate limits, authentication) is not provided, and annotations already cover safety.

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 concise: a one-liner purpose, a contextual paragraph, a default behavior note, and an Args section. Every sentence adds value, and it is front-loaded with the core action.

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 presence of an output schema and comprehensive annotations, the description provides sufficient context: account-wide scope, time range defaults, pagination. Minor missing details like how 'include' or 'team_ids' filters affect results, but schema covers those.

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 input schema has detailed descriptions for all properties (e.g., limit: 'Maximum number of results to return'), so schema coverage is effectively 100%. The description merely lists parameter names ('since, until, limit, offset') without adding new meaning, warranting the baseline of 3.

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 'List all log entries across the account.' It distinguishes from sibling 'get_log_entry' (which retrieves a single entry) and other list tools by specifying an account-wide scope.

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 explains filtering by time range, pagination, and a default of last 7 days. However, it does not explicitly mention when to use this tool over alternatives like 'get_log_entry' for a single entry, leaving usage context implied.

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