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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds pricing and the notion of 'clean structured rows,' but does not disclose details like format auto-detection behavior, header handling, or potential limitations.

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 short and front-loaded with the core purpose. The phrase 'for agents and business workflows' is somewhat generic, but the overall structure is efficient and the pricing note is useful operational context.

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?

The output schema and annotations cover return structure and safety, so the description is not required to explain every detail. However, given the 0% schema coverage and lack of parameter explanations, the description leaves an agent without enough guidance on how to provide the document or configure headerRow.

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%, and the description does not explain the 'document' or 'headerRow' parameters. It only echoes the format enum values (markdown, csv, text), leaving important parameter semantics undocumented.

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 action ('Extract Markdown, CSV, and plain-text tables into clean structured rows') and names the resource and result. It is clearly distinguished from sibling tools like document_structured_extractor by focusing specifically on table extraction.

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 a clear usage context: 'Use when a text or Markdown document contains tables that an agent needs as structured rows.' It does not explicitly list exclusions or alternative sibling tools, but the guidance is sufficient for typical selection.

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