sd_execute_xquery

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

With no annotations provided, the description carries full burden. It explicitly states the tool is read-only, which is a critical behavioral trait. It also mentions it returns raw results as a string, providing transparency about output format. It does not discuss risks or performance implications, but the read-only note is significant.

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 with headings and bullet points. Every section provides necessary information, and the first sentence is a clear summary. The length is appropriate for the tool's complexity, and no content 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?

The description covers purpose, usage guidelines, parameters, and return format. Given the output schema, it doesn't need to detail return values beyond the raw string mention. It is complete enough for a raw query tool, though it could mention error handling or permission requirements.

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%, so the description's Args section is essential. It defines query as an 'XQuery string to execute' and max_results as 'Maximum number of results to return'. These explanations add basic meaning beyond the schema, but lack details like default values or constraints.

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 uses the specific verb 'Execute' and clearly identifies the resource as 'raw XQuery against the database', making the tool's function obvious. It also states its intended audience (advanced users/debugging), which helps distinguish it from common operations. However, it does not explicitly differentiate from the similarly named sibling mop_execute_xquery.

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 includes explicit 'WHEN TO USE' and 'WHEN NOT TO USE' sections, providing clear guidance on usage conditions (advanced/debugging) and exclusions (common operations, write operations). It does not name specific alternative tools, only referring to 'specific tools', which is slightly less actionable.

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