get_user

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

With no annotations provided, the description carries the burden of disclosure. It correctly implies read-only semantics via 'Get' and adds detail about the exclude_fields parameter, including the default behavior and reference to FIELDS.md. It does not mention safety guarantees explicitly but is sufficient for a read operation.

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 efficient: one sentence for purpose, followed by a multi-line explanation of the parameter. No extraneous information. Every sentence adds value.

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 the tool has an output schema (not shown but present), the description need not detail return values. It covers the purpose and parameter behavior thoroughly. The reference to FIELDS.md is appropriate for default exclusion lists. The description is complete for a simple getter with one optional parameter.

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 sole parameter, exclude_fields, has 0% schema description coverage, but the description compensates fully. It explains the default behavior (omission uses model's default from FIELDS.md), how to get all fields ([]), and custom overrides. This adds substantial meaning beyond the schema's basic type definition.

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 begins with 'Get the authenticated user's information,' which uses a specific verb and resource. It clearly distinguishes itself from sibling tools like get_account, get_transaction, etc., which retrieve different entities.

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 description is self-explanatory as a simple getter for the authenticated user. There are no sibling tools with overlapping functionality, so explicit alternatives are not needed. The context of 'authenticated user' implies it should be used when the agent needs information about the current user.

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