laddro.resumes.get

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

Annotations already declare readOnlyHint=true, so the agent knows it's a safe read. The description adds 'Get metadata and content' which is consistent but does not reveal additional behavioral traits (e.g., rate limits, authentication needs). With annotations covering the key behavioral aspect, a score of 3 is appropriate as the description adds no extra value beyond what's already structured.

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 that is front-loaded with the verb and resource, containing zero wasted words. Efficient and to the point.

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 simple get-by-ID tool with only one parameter and an existing output schema (as indicated by 'Has output schema: true'), the description adequately covers the essential information. It could optionally hint at what 'metadata' includes, but the output schema likely fills that gap. Thus, it is complete enough for its simplicity.

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 resumeId described as 'Resume UUID identifier'. The description repeats 'by its ID' without adding new semantics. Since the schema already documents the parameter well, the description does not enhance parameter understanding, earning a baseline 3.

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 verb 'Get', resource 'metadata and content for a specific resume', and method 'by its ID'. It directly and unambiguously differentiates from sibling tools like 'list' (which retrieves multiple) and 'export' (which generates a file).

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 use when you have a resume ID, which is straightforward. No explicit alternatives or exclusions are provided, but given the simplicity and distinct sibling actions, the context is clear enough. A score of 4 reflects clear context without explicit when-not-to-use guidance.

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