export_sheet_to_markdown

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

With no annotations provided, the description carries full behavioral burden and does so thoroughly: it discloses header-row handling, separator insertion, column padding, optional cell-range behavior, and the exact return dict structure including inline vs file-saving differences. This is exemplary transparency for a tool without annotations.

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 and front-loaded with a clear purpose statement, followed by concise parameter bullets and a compact return-value list. Every sentence adds useful information, with no filler or repetition.

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 tool with 4 parameters, no annotations, and no explicit parameter descriptions in the schema, the description is complete: it covers all inputs, edge cases like inline return, and the return contract. An agent has everything it needs to invoke the tool correctly.

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?

Schema description coverage is 0%, but the description fully compensates by explaining every parameter: file_path, sheet_name, output_path (including the special 'return inline' value), and cell_range (including the default behavior of exporting the used range). This adds substantial meaning beyond the bare schema.

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 specific verb ('Export'), a specific resource ('a single Excel sheet'), and the output format ('Markdown table'). It clearly distinguishes this from sibling exporters like export_sheet_to_csv and export_sheet_to_text by its format and scope.

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 makes it clear what the tool does and mentions the important 'return inline' behavior, but it does not explicitly state when to prefer this tool over alternatives like export_sheet_to_csv or get_sheet_data. Usage context is implied rather than explicitly scoped.

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