sophos_get_user

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

The description aligns with the readOnlyHint annotation by using 'Retrieve,' indicating no side effects. It adds value by specifying the kind of details retrieved (permissions, email, profile). No contradictions or missing behavioral traits beyond what annotations cover.

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 extremely concise with two introductory sentences and a brief argument list. Every word serves a purpose—no fluff. Front-loaded with action and use case.

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 that an output schema exists, the description's mention of 'User account details' is sufficient. It does not need to enumerate fields. The description covers the main purpose and usage, though could marginally expand on output structure.

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 50% (username described, client not). The description repeats the username description and adds 'Optional SophosFirewallClient instance' for client, but lacks detail on when or how to use the client parameter. Baseline is appropriate.

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 'Retrieve details for a specific local user account,' using a specific verb and resource. It also gives context for inspection of permissions, email, or profile settings, distinguishing it from sibling tools like sophos_list_users which list all users.

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?

Provides explicit when-to-use guidance: 'Use when inspecting permissions, email, or profile settings for a user.' This implies the tool is for detailed lookup, differentiating from listing tools. No explicit when-not-to-use or alternatives, but the context is clear.

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