get_dp_sql

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

No annotations are provided, so the description carries the full behavioral burden. 'Extracts' implies a read, but the description says nothing about authentication requirements, whether the SQL is cached or requires the DP to have been refreshed, or how errors surface when no SQL has been generated.

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?

A single, front-loaded sentence with no filler; it states the essential operation immediately and stops. Nothing is wasted.

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?

An output schema exists, so return values need not be explained. However, for a tool with two undocumented required parameters and zero annotation coverage, the description leaves genuine gaps around parameter meaning and usage context.

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 mentions neither webi_doc_id nor dp_id. The agent gets no indication of what these identifiers are, their format, or the relationship between the document and the data provider they scope.

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 names a specific verb (extracts) and a specific artifact (the generated SQL query statement of a Data Provider), which is far more precise than a generic 'get DP info'. It does not, however, explicitly distinguish itself from close siblings such as get_dp_specification or get_dp_details, leaving the agent to infer the boundary.

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?

There is no statement of when this tool should be used versus alternatives like get_dp_specification or get_dp_details, and no prerequisites (e.g., whether the DP must be refreshed first for SQL to exist). The agent is given no routing guidance.

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