smartsheet_get_user

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

No annotations are provided, so the description carries full burden. It only states 'Get a single user' without disclosing read-only nature, required permissions, or behavior on non-existent users. This is insufficient for a mutation-free tool.

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 one sentence, extremely concise. However, it is too brief and sacrifices useful information. A slightly longer description with essential details would be more helpful without losing conciseness.

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 simple tool (single required param, no output schema), the description should at least mention what the user object contains or how to handle errors. The current version provides minimal context, leaving the agent underinformed.

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 input schema has 0% description coverage for 'user_id'. The description adds no explanation of the parameter's format, examples, or constraints. The agent must rely solely on the schema type (integer/string), leaving ambiguity.

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?

Description 'Get a single user.' uses a clear verb and resource. It distinguishes from sibling tools like 'smartsheet_get_user_me' (current user) and 'smartsheet_list_users' (multiple users) by specifying 'single'. However, it lacks specificity about what user details are returned.

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?

No guidance on when to use this tool versus alternatives. For example, it doesn't mention that 'smartsheet_get_user_me' is for the current user or that 'smartsheet_list_users' retrieves all users. The agent must infer usage from the name alone.

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