timepiece_export_sync

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds that the export is saved to /tmp and returns a file path and summary, providing context beyond the annotations. No contradiction.

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 description is well-structured with a clear opening sentence and a bulleted Args section. It front-loads the main purpose. It is slightly long but remains readable and informative.

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?

Given the complexity of the tool (nested input object, rich schema descriptions, and an output schema), the description covers the essential purpose and return value. However, it omits potential prerequisites (e.g., Timepiece plugin) and error handling details, making it adequate but not fully complete.

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 description includes an 'Args' section listing parameters with brief types and defaults, adding some meaning beyond the schema. However, the input schema itself has detailed descriptions for each parameter, so the description's contribution is moderate. Schema coverage is 0% per context, but the description compensates partially.

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 clearly states the verb 'Export', the resource 'time-in-status data for Jira issues', and the output format 'XLSX or CSV'. It distinguishes this tool from sibling tools (get, list, aggregate, search) by focusing on file export.

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 implies usage for exporting data to a file but does not explicitly state when to use this tool vs alternatives like timepiece_list_issues or timepiece_aggregate. No exclusions or context-specific guidance is provided.

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