Ruben Marcus — Agent-Ready Portfolio

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the agent knows this is a mutating, side-effectful action. The description adds valuable context by emphasizing 'this delivers a real message', which reinforces the non-idempotent, real-world impact and the importance of the confirmation gate. This goes beyond the annotations without contradicting them.

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?

The description is three short sentences with zero filler. It front-loads the core purpose, then adds the side-effect and the critical usage condition. Every sentence earns its place and the message is delivered in under 30 words, making it efficient for an agent to parse quickly.

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 action tool with no output schema, the description covers everything an agent needs: what it does, the side effect, and the explicit precondition. The parameters are fully documented in the schema, and the description correctly highlights the one decision-relevant context (the confirmation requirement) that isn't in the schema. Nothing essential is missing.

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?

The input schema provides descriptions for all 5 parameters (100% coverage), so the schema already documents each field clearly. The description adds little extra parameter-level meaning: it mentions 'the brief' being relayed, which is already clear from the schema. With full schema coverage, a baseline of 3 is appropriate, and the description does not substantially enhance parameter understanding.

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 opens with a specific verb ('Book') and a distinct resource ('a project intro with Ruben'), and it further clarifies the action by stating it relays the brief to his email. This clearly differentiates it from siblings like check_availability, get_resume, and get_services, which are about checking or retrieving information rather than initiating an action.

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 gives an explicit condition for use: 'Only call after the person you act for has explicitly confirmed', effectively telling the agent when to use it and when not to (before confirmation). It does not name sibling tools as alternatives, but the purpose statement is explicit enough that an agent can infer get_resume/get_services/check_availability are not the same kind of action.

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

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds minimal extra context—only that availability is 'current,' implying time-sensitivity. It does not elaborate on side effects or additional behavior, but the annotations carry most of the burden, so a 3 is appropriate.

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?

The description is a single, front-loaded sentence with no wasted words. It immediately states the core purpose and fully covers the tool's function. This is exemplary conciseness.

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—no parameters, no output schema, and annotations covering safety—the description is fundamentally complete. An agent knows exactly what the tool returns (current availability) and for which contexts (full-time and freelance). Nothing essential is missing for correct invocation.

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?

The tool has zero parameters and the schema is empty with 100% coverage. Since there are no parameters to explain, the description is not expected to add parameter details. Per the rubric, a baseline of 4 applies for zero parameters, and the description does not introduce any ambiguity.

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 states a specific purpose: 'Current availability for full-time roles and freelance contracts.' This clearly identifies the resource (availability) and the type of query, and it inherently distinguishes from sibling tools like book_intro, get_resume, and get_services, which are about different subjects.

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 does not explicitly state when to use this tool versus alternatives. It implies that it is for checking availability, but there is no guidance on when not to use it or when to prefer a sibling. The context is clear from the name, but the description lacks explicit usage direction.

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

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds valuable behavioral context by listing the exact sections of the resume and mentioning a PDF URL, giving agents a concrete idea of the response content. It does not contradict annotations.

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?

The description is a single sentence that front-loads the key information (whose resume) and then enumerates the contents efficiently. Every word earns its place; no fluff or redundant phrasing.

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 zero-parameter, read-only retrieval tool with no output schema, the description is complete. It enumerates the resume sections and includes a PDF URL, covering all likely agent needs. No additional context is required.

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?

The input schema is empty (0 parameters), so schema coverage is 100%. Per the baseline for 0 params, a score of 4 is appropriate. The description adds no parameter meaning because there are none to explain.

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 resource (Ruben Marcus' full resume) and enumerates its contents (summary, work experience, skills, etc.). It distinguishes from sibling tools like book_intro and get_services by focusing solely on the resume. The verb 'get' and the named resource make the purpose unambiguous.

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 clear context: use this tool to retrieve the resume. It doesn't explicitly mention alternatives or exclusions, but the sibling names imply that this is the only tool for resumes. No when-not-to-use guidance is given, but the purpose is so specific that confusion is unlikely.

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

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

Annotations already declare readOnlyHint and idempotentHint, so the agent knows it is safe and idempotent. The description adds that the result is a list of services with pitches, which implies a read operation returning content, but it does not disclose details like response format, ordering, or pagination. Given the annotation coverage, this is adequate but not rich.

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?

The description is a single, tightly worded sentence that immediately conveys the essence of the tool. It is front-loaded with the main point and contains no filler. Perfectly concise.

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?

With no output schema, the description must convey what the tool returns. It indicates a list of services with pitches, but does not specify the structure or fields of each service. Given the tool's simplicity, this might be enough for an agent to anticipate a list, but it leaves out potential details like service IDs, prices, or categories. It is minimally complete but not exhaustive.

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?

There are zero parameters and the schema is empty with 100% coverage. The baseline for 0 params is 4, and the description does not need to add parameter-specific meaning. The description's reference to 'services' and 'pitches' gives a hint of what the output contains, which is sufficient.

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 resource ('services Ruben sells') and the nature of the content ('one-line pitches'). It distinguishes itself from siblings like get_resume (resume data), book_intro (booking), and check_availability (availability checks) by being specifically about services.

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 gives no indication of when to use this tool versus alternatives. There are no exclusions, conditions, or references to sibling tools. An agent gets no guidance on when a call to get_services is appropriate.

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