sap_smart_table_query

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it does so fairly well by enumerating internal steps: metadata fetch, field classification, currency/status recommendations, wrong-customer-field warnings, and field validation. It does not mention potential side effects, authentication requirements, or rate limits, but as a query tool the described behavior is reasonably transparent and not misleading.

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: a one-sentence summary followed by a numbered list of distinct behaviors, ending with a direct usage recommendation. Every sentence adds information, and the structure makes the tool's enhanced behavior easy to parse.

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?

Although the description explains the tool's internal behaviors well, it is incomplete for actual invocation. There is no output schema, no parameters, and no explanation of how the query is provided to the tool. It also only distinguishes itself from one of many sibling table-reading tools, leaving ambiguity in a large sibling set. An agent cannot reliably call this tool based on the current definition.

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 zero properties, yet the description promises to 'Execute a table query' and references fields, currency filtering, status exclusion, and customer fields. There is no explanation of how the agent should specify the table name, query conditions, or field selections. Even with the '0 params = baseline 4' heuristic, this tool clearly requires inputs, and the description does not compensate for the empty schema at all.

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 'Execute a table query with automatic metadata-driven enhancements' and lists four concrete behaviors: metadata fetching, field classification, recommendations, warnings, and validation. It also explicitly differentiates itself from sap_read_table_data by saying to use this tool instead when intelligent guidance is wanted.

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 an explicit alternative and a usage condition: 'Use this instead of sap_read_table_data when you want intelligent guidance!' This gives an agent a clear signal for when to select this tool over a key sibling. However, it does not articulate any when-not conditions or contrast with other sibling tools like sap_read_table_data_enhanced or sap_multi_table_query.

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