get_profile_info

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

No annotations are provided, so the description carries the full behavioral burden. It implies retrieval for the signed-in employee but does not state read-only status, permission requirements, side effects, or return behavior, leaving meaningful behavioral gaps for an unannotated 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?

The description is a single concise fragment with no filler and is front-loaded. It is appropriately sized for a zero-parameter getter, though the lack of a verb makes it slightly less structured than a complete sentence.

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 zero-parameter getter with no output schema, the description still does not explain what fields are in the 'profile header' or how it differs from adjacent profile-oriented siblings. Given the dense sibling list, the description is too terse to fully orient an agent.

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 parameter semantics are not applicable and the baseline is 4. The empty schema is fully covered, and the description does not need to explain parameter usage.

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 identifies the resource and scope: 'Signed-in employee's profile header.' However, it omits an explicit action verb, relying on the tool name to convey retrieval. Among many profile-related siblings such as get_profile_completion, get_timesheet_profile, and get_id_card, it does not explicitly distinguish what a 'profile header' includes versus those alternatives.

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?

There is no when-to-use, when-not-to-use, or alternative-tool guidance. The phrase 'Signed-in employee's profile header' only restates the likely target data and does not help an agent choose between this and sibling profile tools.

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