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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description's "read-only export" merely restates that safety profile. It adds the endpoint path and a vague "pass data in the API-supported format" note but discloses nothing about auth requirements, return format, or limits. With annotations carrying the safety burden, this is adequate but adds little genuine context.

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 short sentences that are front-loaded with the core action and contain no padding. The second sentence is somewhat vague but still earns its place as a constraint statement.

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 9-parameter export tool with no output schema and only partial schema coverage, the description omits what the export produces, what format the result takes, and how the data parameter works. An agent would struggle to call this correctly, especially the data argument.

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?

With 9 parameters and only 56% schema description coverage, the description should compensate for the undocumented to/data/from/user_id arguments but does not. "Pass data in the API-supported format" gestures at the data parameter without explaining its structure, acceptable values, or relationship to from/to.

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 ("Exports timecards") and even names the endpoint GET /timecards/export, so the basic action is unambiguous. However, it does not distinguish this tool from closely related siblings such as export_invoice, list_timecards, get_timecard, or generate_timecard, so the agent gets no help telling similar export/list/get operations apart.

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?

There is no guidance on when to use this tool versus list_timecards, get_timecard, or export_invoice. The "Limitations" line describes a constraint, not a usage condition, and no prerequisites or exclusions are given, leaving selection entirely to inference.

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