asana_get_user

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

With no annotations provided, the description bears the full burden of behavioral disclosure. It states it retrieves user details, which is a simple read operation, but does not mention any behavioral traits such as authentication requirements, rate limits, error handling, or the specific scope of the returned data.

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 a single sentence of 13 words that is front-loaded with the purpose. Every word adds value, with no redundancy or filler. It is appropriately sized for the tool's simplicity.

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 simple get-user tool with two parameters and no output schema, the description adequately covers the function, key input, and expected output fields. It could be slightly more specific about the full list of returned fields, but given the tool's simplicity and standard API conventions, it is sufficient.

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 description adds meaning to the required `user_gid` parameter by explaining valid values: 'GID (or "me")'. This compensates for the lack of a description in the schema. The `opt_fields` parameter already has a schema description, so no additional value needed.

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 the verb 'Get', resource 'Asana user', and specifies the key parameter 'by GID (or "me")' and the kind of data returned ('name, email, etc.'). It effectively distinguishes from sibling tools like asana_get_task (different resource) and asana_list_tasks (different action).

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 implies the tool is for retrieving a single user by GID, but it does not explicitly state when to use this versus alternatives like search tools, nor does it mention any prerequisites or exclusions. The context from sibling tools is not leveraged in the description.

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