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

readOnlyHint=true already establishes this as a safe read, so the description doesn't need to restate safety. It does add content-scope information (profile, access, roles), which tells the agent this returns permission data rather than just a name. It discloses nothing about sensitivity, authorization requirements, or what happens for an unknown ID.

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 short sentences with no filler, and the capability is front-loaded ahead of the usage hint. Nothing is padded, though the second sentence is thin enough that it could have carried the missing alternative-tool guidance instead.

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 single-parameter read tool with no output schema, the agent knows what it gets (profile, access, roles) and the entry condition (a userID). The unresolved gap is how to obtain that userID and why this beats user_search, which the description leaves entirely to inference.

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?

Schema description coverage is 100% for the single userID parameter (uuid format, 'Employee ID'), so the schema carries the load. The description's 'by userID' merely confirms lookup-by-identifier behaviour and adds no format or validation detail beyond the schema.

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 and resource: returns an employee's profile, access and roles, keyed by userID, which is materially more informative than the tautological title 'User context'. It does not, however, distinguish itself from the sibling user_search, which an agent could easily confuse it with.

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?

'Useful when the user asks about a specific colleague' gives implied usage context, but the crucial precondition — that you must already hold a userID and should use user_search to obtain one — is never stated or excluded. There is no explicit when-not or alternative routing.

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