Info User

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

No annotations are provided, so the description carries the burden. 'Fetch' and 'authenticated user' signal a read-only operation and an authentication requirement, which is helpful. However, it does not disclose authorization details for sub-users, behavior on invalid IDs, or the structure of returned info, leaving partial transparency.

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 13-word sentence that efficiently communicates both the core purpose and the key parameter distinction with no unnecessary words.

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?

The tool is simple (one optional parameter) and the description covers the basic purpose and parameter semantics. However, with no output schema or annotations, it does not specify what 'info' is returned, error behavior, or any permissions beyond the word 'authenticated,' leaving minor but real gaps.

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 schema has one nullable integer parameter with no description, and the description directly explains its semantics: null (default) fetches the authenticated user, while providing an id fetches a sub-user. This fully compensates for the 0% schema description coverage.

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 'Fetch info about the authenticated user, or a specific sub-user by id.' It uses a specific verb ('fetch'), identifies the resource ('user'), and distinguishes between two distinct use cases (self vs sub-user), setting it apart from sibling info_* tools.

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 when to use the tool (when needing user info) but does not explicitly discuss alternatives or exclusions. It does not mention other tools like info_contact or info_domain, and it lacks definitive 'when to use / when not to use' guidance.

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