get_files_by_connector

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the basic read operation, without mentioning pagination (top), ordering (orderby), return format, error handling, or any side effects. This is minimal for a tool that actually has pagination and sorting parameters.

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, front-loaded sentence with no wasted words. Every word contributes to the core purpose, making it exceptionally concise and 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?

For a tool with no annotations and no output schema, the description is incomplete. It does not explain the return value (what fields are included), the effect of pagination parameters (top, orderby), or error scenarios. Given the presence of these parameters and the many sibling tools, more context is needed for correct usage.

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 100% with descriptive text for all three parameters (connectorId, top, orderby). The description adds no additional parameter semantics beyond the schema, but the baseline for fully covered schemas is 3, and the schema itself provides sufficient meaning.

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 action ('Get') and resource ('files') with a specific scope ('processed by a specific connector'). This distinguishes it from sibling tools like list_files or get_recent_files, which have broader or different filtering. The phrase 'specific connector' immediately conveys the unique purpose.

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 does not explicitly state when to use this tool versus alternatives, nor does it mention exclusions or provide context beyond the connector filter. The use case is only implied by the phrase 'by a specific connector', but there is no guidance on when this is preferable to list_files or get_recent_files.

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