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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety bar is low. The description adds the key behavioral fact that annotations cannot convey: the result is scoped to the authenticated caller's own record, not an arbitrary user's, and it itemizes what state is exposed including verification state.

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?

One front-loaded sentence with a colon-list of fields and zero filler. It is a noun phrase rather than a full sentence, but every word earns its place and nothing is buried.

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's field enumeration is the only source of return-content information, and it is adequate for a zero-arg read. Minor gaps remain: no mention of behavior when no profile exists or whether fields can be empty.

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?

Zero parameters and 100% schema coverage, so nothing needs documenting; the description correctly adds no parameter talk and instead spends its words on the return payload.

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?

States a specific verb+resource: reads the signed-in person's own directory profile, and enumerates its contents (job role, rate, verification state). 'Own' distinguishes it from a generic directory lookup, though it never names a sibling such as directory_capabilities explicitly.

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?

Usage is only implied: 'the signed-in person's own' tells the agent this is caller-scoped and read-only, but there is no statement of when to call it versus propose_profile_update or directory_capabilities, nor any prerequisite such as authentication.

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