list_resumes

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

No annotations are provided, so the description carries full burden. It discloses that it returns all resumes (implying no filtering) and includes primary and alternate versions, but lacks details on permissions, rate limits, pagination, or error behavior. The description is accurate but minimal for a read operation.

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?

Two concise sentences front-load the core action and scope, with no wasted words. The first sentence states the purpose, and the second elaborates on what's included, earning its place by clarifying the return content.

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 low complexity (1 optional parameter, no output schema, no annotations), the description is reasonably complete for a list operation. It covers what is returned but lacks details on format, ordering, or limitations. For a simple tool, this is adequate but not exhaustive.

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 input schema has 1 parameter with 100% coverage, so the baseline is 3. The description does not mention the parameter 'includeRawTxt', but since there are 0 required parameters and the schema fully describes it, this is acceptable. No additional parameter semantics are provided, but the tool's purpose is clear without them.

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 'List' and the resource 'your uploaded resumes', specifying scope with 'all resumes you have uploaded to your profile, including your primary resume and any alternate versions'. It distinguishes from sibling tools like 'get_resume' (singular) and 'upload_resume' (upload action).

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 implies usage for retrieving all uploaded resumes, but does not explicitly state when to use this tool versus alternatives like 'get_resume' (for a specific resume) or 'list_generated_resumes' (for AI-generated ones). No exclusions or prerequisites are mentioned.

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