get_resume

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

The description discloses the source (resume_path from profile), return type (raw text), and supported formats. With no annotations, this transparency is good, though it omits potential failure modes (e.g., file not found).

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 with no unnecessary words. The key points (read resume, source, return type, formats) are front-loaded. 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?

For a parameterless tool with no output schema, the description covers what the tool does, where it gets data, and what it returns. It is fully sufficient 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?

No parameters exist, so the description naturally adds meaning by explaining the data source (saved profile) and file formats. The baseline is 4 as there are no parameters to describe.

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 reads the resume file with a specific verb-resource combination. It distinguishes from siblings like get_profile (profile) and add_resume (adding) by focusing on reading the existing resume.

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 the tool should be used to read the resume, but does not explicitly state when to use it versus alternatives (e.g., get_profile for profile info, add_resume for uploading). No when-not-to-use guidance is provided.

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