get_all_resource_file_names

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

The description provides minimal behavioral information. It does not mention that the tool is read-only, the format of returned names, pagination behavior, or any requirements. With no annotations, the description carries the full burden but fails to disclose important traits.

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 very concise, using a single sentence with no filler. However, it is under-specified; conciseness should not sacrifice completeness.

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?

Despite the presence of an output schema, the description is insufficient. It does not clarify that the tool returns all names (possibly paginated), nor does it mention the role of offset and count. The absence of annotations increases the need for a more complete description.

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 description adds no meaning to the parameters 'offset' and 'count', which have 0% schema coverage. These parameters control pagination, but the description does not explain their purpose or effect.

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 verb 'retrieve' and the resource 'all resource files names', indicating the tool returns a list of file names. However, it does not differentiate from the sibling tool 'get_resource_file' which likely retrieves a single file's content.

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?

No guidance is provided on when to use this tool versus alternatives like 'get_resource_file' or others in the sibling list. The description lacks any context on prerequisites or scenarios.

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