tempo_search_timesheet_approval_logs

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

Annotations already declare readOnlyHint=true, and the description is consistent with that. It adds valuable context beyond the annotation: permission requirements, a PII warning (account ids, reviewer actions), and the pagination behavior via nextPageToken. This gives an agent meaningful operational expectations that structured fields alone would not.

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?

Three short sentences with zero waste: purpose first, then safety/permission caveats, then pagination mechanics. Each sentence carries distinct, necessary information and nothing is repeated from the schema.

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?

For an optional-parameter search tool with no output schema, the description covers the key operational concerns: permission prerequisites, PII sensitivity, and pagination. The view parameter's schema text fills in response-shape details. It stops short of describing the returned log entry fields or any sort ordering, but the essentials an agent needs before invoking are present.

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 description coverage is 100%, so the schema already documents all five parameters, including a rich explanation of the view enum and date formatting for updatedFrom. The description adds only the pagination behavior already reflected in nextPageToken's schema text, so it stays at the baseline rather than adding new parameter-level meaning.

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 opens with a specific verb+resource ('Search timesheet approval audit logs'), and the word 'audit logs' clearly separates this tool from the approval-lifecycle siblings such as tempo_get_timesheet_approval_status, tempo_get_timesheet_approvals_waiting, and tempo_approve_timesheet. An agent can distinguish the historical audit-trail intent from current-status or mutation tools without opening any schema.

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 'audit logs' framing implies this is for historical investigation rather than checking current approval state, but no alternative sibling is named and no when-to-use vs. when-not-to-use condition is stated. The PII and permission warnings hint at appropriate contexts, but the agent must infer the routing versus the many approval-status siblings.

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