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

The description provides critical operational behavior beyond the annotations by specifying the exact cost structure: 'Costs 1 credit + 2 credits per profile returned.' This is vital information for an agent managing resource constraints.

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 definition is extremely concise and well-structured. The first sentence defines the resource and scope, and the second sentence provides the essential operational metadata (cost), utilizing every sentence efficiently.

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?

Despite lacking an explicit output schema, the description exhaustively lists every single field returned by the API. Combined with the operational cost, this makes the tool definition maximally complete for agent invocation and planning.

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 description coverage is 100%, meaning the input schema already provides a thorough description of the 'user' parameter. The description focuses on the output data and costs, not the input semantics, making the baseline score of 3 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 the tool's purpose is to fetch a 'public X profile.' It goes beyond a generic statement by listing all the specific attributes returned (name, followersCount, verified, etc.).

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 explicitly frames the tool's scope as fetching a 'public X profile,' which provides clear context on its usage boundaries. While it doesn't list usage scenarios, the scope definition is strong enough to guide agent selection.

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