get_gql_user_web_profile_info

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

No annotations provided, so description carries full burden. Only states 'Get user profile info' with no details on returned structure, side effects, permissions, or rate limits. Lacks necessary behavioral disclosure.

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?

Short but repetitive: repeats 'Get user profile info' and 'GraphQL web_profile_info' in two lines. Could be combined into one concise sentence.

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 tool with one required parameter and many siblings, the description is too sparse. It lacks detail on what kind of profile info is returned, authentication needs, and how it differs from other user info endpoints.

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?

Schema coverage is 0%, yet description only adds 'by user id' to the parameter. No format, example, or constraint explanation beyond the schema field name.

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?

States verb+resource clearly: 'Get user profile info by user id'. However, does not differentiate from many sibling tools like get_v1_user_about, get_v2_user_by_id, etc. The mention of GraphQL is subtle but not explicitly justified.

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 the numerous similar sibling tools. No mention of prerequisites, context, or exclusions.

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