List org Drop files

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds the org-scoping context and the endpoint, but does not disclose additional behavioral traits such as pagination, response format, or rate limits. With annotations doing the heavy lifting, this is adequate but not enriched.

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 that states the purpose and endpoint without wasted words. Every element earns its place.

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 a single parameter, no output schema, and good annotations, the description is minimally viable for a simple list operation. However, it lacks any mention of pagination, response fields, or how it differs from drop_files_list, leaving some gaps for a fully informed agent.

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 schema has one parameter, org_id, with no description (coverage 0%). The tool description does not explain org_id directly, only implying it through 'Org-scoped' and the '{id}' placeholder in the endpoint. This adds little beyond the parameter's self-explanatory name.

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 lists org-scoped Drop file metadata, with the specific verb 'list' and resource 'Drop file metadata'. The endpoint 'GET /orgs/{id}/drop/files' further specifies the exact operation. The 'Org-scoped' qualifier distinguishes it from the sibling drop_files_list, which likely operates at a different scope.

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 explicitly notes the org-scoped nature, providing clear context for when to use this tool (when needing files belonging to an org). However, it does not name alternative tools like drop_files_list or provide explicit 'when not to use' guidance, so it stops short of a 5.

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