get-table-sample-data-by-name

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

No annotations are provided, so the description must fully disclose behavior. It only states it 'gets sample data rows', implying a read operation, but does not mention any limits, permissions, or potential side effects. This is insufficient for transparent behavior.

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 a single, well-structured sentence that immediately conveys the purpose. No filler or redundant information. Perfectly concise for the complexity.

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?

Despite having only one well-documented parameter, the description lacks information about the return format, number of rows, or prerequisites. With no output schema, the agent cannot fully anticipate the tool's behavior. Additional context like 'returns a list of row objects' would improve completeness.

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?

There is one parameter 'fqn' with clear schema description (including example). Schema coverage is 100%, so the description adds no extra meaning. Baseline score of 3 is appropriate as the schema does the job.

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 verb 'Get', the resource 'sample data rows for a table', and the method 'by fully qualified name'. It distinguishes from sibling tools like 'get-table-sample-data' by specifying the use of fully qualified name, and from container counterparts by specifying 'table'.

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 no guidance on when to use this tool vs alternatives such as 'get-table-sample-data' (which might use a different identifier) or other sample data tools. No when-not-to-use or context hints are given.

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