swsd_get_user

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description's main addition is the field list, which largely duplicates the supplied output schema; it says nothing about behavior on a missing or invalid id, or whether disabled users are still returned. Useful, but only modest value beyond the structured fields.

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 sentences, front-loaded with the action and scope, then the return payload, then the prerequisite. Nothing is redundant filler and the ordering matches how an agent would plan the call.

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?

A read-only, single-parameter getter with full annotation coverage and an output schema — the description covers action, payload, and how to obtain the id, so nothing needed to call it correctly is missing.

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% and the single parameter already documents that the id comes "from the matching swsd_list_* tool." The description repeats that hint via swsd_list_users without adding format, range, or error semantics, so the baseline of 3 applies.

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 ("Fetch one SWSD user by id") and enumerates the returned fields, which clearly separates it from the sibling listing tool swsd_list_users. An agent can distinguish it from the other swsd_get_* tools (role, group, site, department) without opening any schema.

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?

Explicitly prescribes the workflow "Use swsd_list_users first to find the id by name or email," so the agent knows this tool requires an id it likely doesn't have yet. It does not state a when-not condition (e.g., bulk lookup), but for a single-record getter 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.