get_quick_apply_profile

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

No annotations are provided, so the description must carry the burden. 'Get' implies a read-only operation and lists return contents, but does not disclose authentication requirements, potential null cases, or any side effects. This is adequate but minimal.

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 concisely lists the key data categories. It includes 'for auto-filling job applications' which adds context but could be trimmed. Overall efficient.

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 no output schema, the description covers the main return fields (work authorization, salary, availability, etc.). It does not specify the exact structure or error handling, but for a zero-parameter getter, it is largely complete.

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 has 0 parameters with 100% schema description coverage. Baseline is 3. The description adds no parameter details but does list the data fields returned, which is beyond the empty schema. No parameter guidance is needed.

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 retrieves the user's Quick Apply profile data and lists specific fields (work authorization, salary expectations, etc.). It distinguishes itself from sibling tools like 'update_quick_apply_profile' and 'clear_quick_apply_profile' by focusing on retrieval.

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 usage for viewing or obtaining Quick Apply data, but does not explicitly state when to use this vs. alternatives. However, with no parameters and a clear read-only intent, the usage is straightforward and self-evident.

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