list_resume_summaries

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

Describes the lightweight nature, token efficiency, and pagination fields (total_count, items). No annotations are present, so the description carries the full burden. It doesn't mention auth or rate limits, but the behavior is straightforward and non-destructive.

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?

Three concise sentences, front-loaded with purpose, no wasted words. Every sentence adds value.

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, an output schema exists (though not shown), so return values are covered. The description covers identity, purpose, efficiency, and pagination. It is complete for an agent to understand and invoke correctly.

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 clear parameter descriptions (limit, offset with defaults). The description does not add extra meaning beyond the schema, which already explains them. Baseline 3 is appropriate.

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 it lists lightweight identity records (id, name, email, phone only), which is a specific verb+resource combination. It distinguishes from 'list_resumes' (presumably full resumes) and other siblings by emphasizing the lightweight nature.

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?

Explicitly says 'Use this to orient and pick a resume_id before fetching details with other tools' and compares to 'list_resumes' as more token-efficient for identification purposes. Clear guidance on when and why to use it.

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