get-forum-user

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action and does not describe what 'profile information' includes, the return format, error handling for unknown usernames, or any authentication requirements. Minimal behavioral 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, concise sentence (11 words) that is front-loaded with the verb and resource. Every word is necessary, and there is no wasted or redundant text.

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 parameter) and the description covers the basic purpose, but with no output schema and no annotations, it leaves gaps such as the structure of the returned profile and possible error responses. Adequate for a low-complexity tool, but not fully complete.

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 already fully documents the single parameter 'username' with a clear description, and schema coverage is 100%. The description's phrase 'by username' adds no additional meaning beyond the schema, so the baseline score of 3 is appropriate.

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 an unambiguous action: 'Get a VEX Forum user's profile information by username.' It specifies the resource (VEX Forum user profile), the method (by username), and is distinct from sibling tools like search-forum or get-forum-topic, which handle content rather than user profiles.

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?

Usage is implied by the tool's unique purpose among siblings (no other tool retrieves user profiles), but there is no explicit guidance on when to use this tool versus alternatives, nor any mention of prerequisites or edge cases. The description relies on the user inferring when to use it.

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