pyp6xer_get_upload_url

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds that the tool provides instructions (not performing uploads), which aligns with the read-only nature. It does not disclose additional behavioral details beyond annotations, but annotations are sufficient.

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 concise sentences that each serve a purpose: stating the tool's function and providing context about local server usage. No unnecessary words or redundancy.

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 no parameters, an existing output schema (not shown but present), and rich annotations, the description is complete. It tells the agent exactly what the tool does and how it fits with sibling tools. No additional information seems needed.

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 has no parameters, so schema coverage is 100%. The description does not need to add parameter info. Per the guidelines, with 0 params baseline is 4, and the description does not detract.

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's purpose: 'Get instructions for uploading an XER file to this server.' The verb 'Get instructions' is specific, and the resource 'upload instructions' is explicit. It distinguishes from sibling tools like pyp6xer_load_file by indicating that this tool provides instructions, while loading is done via the sibling.

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 provides context about when to use this tool: it gives instructions for uploading, and notes that on this local server, files are loaded via pyp6xer_load_file. This implicitly tells the agent to use this tool for instructions and the sibling for actual loading. However, it lacks explicit 'when not to use' or alternative scenarios.

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