getPersonalDetails

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

With no annotations, the description carries the full burden. It discloses the login side effect and the live nature of the lookup, which adds behavioral context. It does not detail authentication requirements or session implications, but for a simple fetch operation this is reasonably transparent.

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?

Two efficient sentences that front-load the verb and resource, list the retrieved fields, and provide a key behavioral note. No redundant or filler content.

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?

The tool is simple (1 optional param, no output schema). The description covers what it does and a key contextual detail ('live lookup'). It lacks return format details, but given the low complexity and field enumeration, it is sufficiently complete for an agent to select and invoke the tool.

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 schema has 100% parameter description coverage, including the 'tenant' field's purpose. The description adds no new parameter semantics, so the baseline of 3 applies as per the rubric.

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 uses a specific verb ('fetches') and clearly identifies the resource ('personal details') with an enumerated list of fields. It distinguishes itself from sibling tools like syncPayslips and query, which deal with other data or local database operations.

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 statement 'This is a live lookup, not stored in the local database' provides clear context for when to use this tool (when fresh data is needed) and implicitly contrasts with local DB tools like query. However, it does not explicitly name alternative tools or provide exclusion scenarios.

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