pyp6xer_export_xer

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

Annotations (readOnlyHint=true, destructiveHint=false, idempotentHint=true) indicate safe, non-destructive behavior. The description adds value by explaining the base64 encoding rationale and that it exports the current in-memory schedule, which complements the annotations without 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 extremely concise with two sentences. The first sentence states the primary action, and the second explains the encoding rationale. Every sentence adds value with no extraneous text.

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 presence of an output schema (as indicated by context signals), the description does not need to detail return values. It covers the tool's purpose and the reason for base64 encoding. It could mention the prerequisite of a loaded schedule, but that is implied by 'current schedule'. Overall, it is sufficiently complete for a simple tool with one optional parameter.

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 input schema already provides a description for the single parameter (cache_key) with 100% coverage. The description does not add additional context about the parameter, so the baseline score of 3 is appropriate.

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 tool exports the current schedule as base64-encoded XER bytes, providing a specific verb and resource. It distinguishes from sibling export tools like pyp6xer_export_csv by specifying the format (XER vs CSV) and the encoding reason (base64 for file download without local path).

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 after loading a schedule via pyp6xer_load_file by referring to the 'current (possibly modified) schedule'. It provides clear context for when to use this tool (to get XER data for download) but does not explicitly mention alternatives like pyp6xer_export_csv or pyp6xer_write_file, which is a minor gap.

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