Get user profile

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

With no annotations, the description carries the full burden of behavioral disclosure. It states it 'Return' data, implying a read-only operation, but does not explicitly say it has no side effects, requires no authentication, or what happens if the profile is incomplete. The mention of 'still-missing fields' hints at returned status but is minimal. No error conditions or output format are described.

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 that states the core action and key output. It is concise with no wasted words. However, it may be too brief for a tool with no output schema, but for a simple getter it is appropriately compact.

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 there is no output schema, the description should explain the return structure and key concepts. It mentions 'Master Profile' and 'still-missing fields' but does not elaborate on what these contain or how they are represented. It also lacks usage context and alternatives, which a zero-param tool with no schema could benefit from. It is minimally sufficient but not thorough.

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, so the baseline is 4. The description does not need to explain parameters, and since schema coverage is trivially 100%, there is no gap. The description adds no parameter-specific meaning, which is acceptable for a param-free tool.

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 returns the current Master Profile and lists missing fields. The verb 'Return' and resource 'Master Profile' make the purpose specific and distinguish it from setup/update tools that modify profiles. However, it doesn't explicitly differentiate from siblings like analyze_master_resume, but the intent is evident.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, typical scenarios, or exclusions. With 16 siblings, an agent would have to infer that this is for reading the profile, but nothing states when to call it over update_user_profile or setup_user_profile.

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