Search_SharePoint

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

The description mentions returning up to row_limit results with metadata and notes KQL usage, but lacks detail on authentication, error handling, or rate limits. Given no annotations, more transparency would be beneficial.

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 consists of two concise sentences that front-load the core purpose and usage context, with no unnecessary words.

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?

Given the tool's simplicity (two parameters, output schema exists), the description covers the main use case but omits details like query syntax examples or what metadata fields are returned, which would aid usability.

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 coverage is 0%, so the description must compensate. It mentions KQL (relating to query) and row_limit as a cap, but does not explain valid formats or the default behavior beyond the schema's default of 20.

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 searches SharePoint for documents using KQL, specifying a distinct action and resource that differentiates it from sibling tools like Create_Folder or Download_Document.

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 indicates when to use the tool: 'when you don't know their exact folder path.' While it doesn't explicitly mention alternatives, the sibling tools list implies alternatives for known paths.

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