get_resume_profile

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

No annotations provided; description carries full burden. Discloses what data is included and excluded, which is sufficient for a simple read operation. Does not mention auth or rate limits, but these are not expected for such a tool.

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?

Single sentence, concise and front-loaded with purpose. No wasted words, and the exclusion clause adds precision without verbosity.

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 (one parameter, output schema exists), the description is complete. It clearly differentiates from siblings and covers what the tool returns and omits.

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 has 100% coverage on resume_id with description. The description adds extra context by specifying where to obtain the resume_id (list_resume_summaries or search_resumes_by_name), which aids correct invocation.

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?

Description clearly states the tool retrieves top-level fields of a resume (contact info, professional statement, education) and explicitly excludes nested work experience and badge skill lists. This distinguishes it from siblings like get_resume, get_work_experience, and get_badge_skill.

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?

Implicitly indicates when to use (for top-level fields only) by contrast with excluded nested lists. Does not explicitly name alternatives or state when not to use, but the sibling context provides that context.

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