tempo_get_timesheet_approval_status

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

Annotations declare readOnlyHint=true and openWorldHint=true, so the agent knows this is a safe read operation from an open system. The description adds a critical security warning about untrusted third-party content, which is valuable behavioral context. However, it does not describe the return format, pagination, or error conditions beyond the generic warning.

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?

Two sentences that are front-loaded and efficient. The first sentence states the purpose, and the second provides an important safety warning. No wasted words, though the warning could be integrated more seamlessly.

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 a read-only tool with full schema coverage and no output schema, the description covers the purpose and adds a crucial trust warning. However, it lacks guidance on when to use this tool versus similar approval status tools and does not describe the shape of the returned status data, which could be important for an agent to interpret results correctly.

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 parameters, including the view enum and date formats. The description adds no parameter-specific details beyond what the schema provides, which is the baseline when the schema does the heavy lifting.

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: retrieve the current timesheet approval status for a user in the given period. This clearly distinguishes it from sibling action tools like tempo_submit_timesheet or tempo_approve_timesheet. However, it does not explicitly differentiate from tempo_get_timesheet_approvals_waiting or tempo_get_timesheet_approvals_by_team, leaving the agent to infer the distinction.

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 explicit guidance on when to use this tool versus alternatives such as tempo_get_timesheet_approvals_waiting or tempo_get_timesheet_approvals_by_team. The context is implied by the tool's purpose but not stated, leaving the agent to infer usage conditions.

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