Get clock status

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered by structured data. The description adds real value by disclosing the backing source ('Contractor Foreman Time Cards dashboard') and the exact shape of what comes back, which matters because there is no output schema. It does not mention permission scoping (e.g. whether results are limited to projects the user can see).

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 lead sentence front-loads the three things an agent gets, and the second sentence supplies detail. The second sentence is long and enumerative, but given the absence of an output schema that detail earns its place.

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 carries the burden of explaining return values and does so thoroughly — current clock-ins, the caller's own status plus card id, and week-over-week hour breakdowns by category. What is missing is any note on empty-state behavior (what happens when nobody is clocked in) or scope/visibility limits.

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 tool takes zero parameters, so the baseline is 4. The description correctly implies no input is needed, framing the call as a context-free snapshot.

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 states a concrete verb+resource ('Who is clocked in right now... crew hours') and enumerates exactly what is covered: current clock-ins with project and time, the signed-in user's own status and card id, and team/user regular/overtime/total hours for this and last week. It is clearly distinct from list_time_cards and list_project_crew_hours in substance, though it never names those siblings, which is the only thing keeping it from a 5.

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?

'Right now' implies the snapshot use case, but there is no explicit statement of when to call this versus list_time_cards or list_project_crew_hours, and no prerequisites or exclusions are given. Usage is inferable from the described output rather than stated.

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