get-schema

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

Annotations set idempotentHint=true, confirming safe reuse. The description adds behavioral context by explaining how to interpret the response (columnName properties) and providing a concrete example. No contradictions with 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?

Three sentences, no filler. First sentence defines the action, second explains how to extract column names, third provides an illustrative example. Every sentence adds value, and the structure is front-loaded.

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 2 required parameters, existing output schema, and idempotent annotation, the description adequately covers purpose and response interpretation. Lacks explicit error scenarios or prerequisites beyond parameter descriptions, but overall complete enough.

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?

Both parameters (dataflowId, executionId) have clear descriptions in the input schema, achieving 100% schema coverage. The description does not add additional meaning to these parameters, focusing instead on the output format. Baseline 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 'Get data table schema from a Coupler.io data flow' with a specific verb and resource. It distinguishes from siblings by focusing on schema retrieval, differentiating from get-data (data), get-dataflow (metadata), and list-dataflows (enumeration).

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 does not explicitly state when to use this tool versus alternatives. It implies usage for obtaining column names before fetching data, but lacks explicit when-to-use or when-not-to-use guidance. The example helps but does not clarify selection criteria.

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