list_resume_summaries

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

The description clearly states what the tool returns (lightweight identity records) and its token-efficiency benefit. With no annotations provided, it carries full burden and does well, though could mention ordering or limits. Still very transparent.

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 redundancy. 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 (0 params, output schema exists), the description fully covers what an agent needs: what is returned, when to use, and efficiency trade-off.

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?

No parameters exist (0 params, schema coverage 100%). The description adds no parameter info but that is unnecessary. Baseline 4 for 0 params 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 explicitly states it lists resumes as lightweight identity records with specific fields (id, name, email, phone). It clearly distinguishes itself from sibling list_resumes by highlighting token efficiency and limited fields.

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 provides direct usage guidance: use this to orient and pick a resume_id before fetching details with other tools. This explicitly tells when to use and implies when not to use (when full details are needed).

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