tempo_search_timesheet_approval_logs

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

Goes well beyond the readOnly/openWorld annotations: it discloses the permissions requirement, warns that results may contain PII, explains pagination via nextPageToken from the previous response, and flags returned text as third-party and untrusted (prompt-injection warning). This is exactly the behavioral context annotations cannot carry.

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?

Four short sentences, front-loaded with purpose then permissions, pagination, and the security caveat. No filler, every sentence carries distinct 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?

With no output schema, the description does useful work by covering pagination, PII in results, and untrusted content, plus the view parameter governs response shape. It stops short of describing the return payload's structure, but the essentials for correct invocation 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 the view enum and the date-range format. The description only reinforces nextPageToken pagination, adding little beyond the structured fields; baseline 3 applies.

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?

States a specific verb and resource: 'Search timesheet approval audit logs.' This is reasonably distinct from the approval-workflow siblings (approve/reject/status), but it never explicitly contrasts itself with tempo_get_timesheet_approval_status or tempo_get_timesheet_approvals_waiting, which an agent could easily confuse with an 'approval' search.

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 states a permission prerequisite but gives no when-to-use vs when-not guidance and never names an alternative tool. The agent must infer from the name alone that this is the audit-log view rather than the approval-status view.

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