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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable beyond-annotation context: a hard batch limit of 100 and pricing behavior of 1 credit per profile found.

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?

Two short sentences, no filler, and the most important scoping constraint (up to 100 users by handle in one call) is front-loaded. The credit cost is added as a natural second 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?

The description plus schema give an agent the required handle input, the optional fresh flag, the batch limit, and cost behavior. It is complete for invoking the tool correctly, though an explicit note about the return shape for missing handles would strengthen it further.

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 only 50%; the handles parameter lacks a description in the schema. The description compensates by clarifying that the array values are X handles and that the call accepts multiple users up to 100. The fresh parameter is already described well in the schema.

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 states exactly what the tool does: fetches profiles for up to 100 X users by handle in one call. The title 'Profiles, batch' and the sibling name get_user make the batch-vs-single distinction immediately clear.

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 batch usage with 'up to 100 X users by handle in one call' and the sibling get_user exists for single-user lookups. However, it never explicitly says when to choose this tool over get_user or when not to use it, so the guidance is implied rather than stated.

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