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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the shape of the returned data, which is real value given no output schema, but it says nothing about read-only safety, authentication, rate limits, or behavior on an unknown/nonexistent handle.

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 sentences, front-loaded with the action and returned fields, then the use case. No filler or repetition; every clause adds information.

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?

With no output schema and no annotations, the description compensates well by listing the returned fields in place of a return-value spec. Remaining gaps are minor operational details (auth, errors, read-only confirmation) rather than anything needed to invoke it correctly.

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% and the single 'handle' parameter is already documented in the schema, including the leading-@ tolerance and an example. The description only restates 'by handle' and adds no syntax or format meaning beyond that, so baseline 3 applies.

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 a specific verb and resource ('Get a creator or brand profile by handle') and enumerates the exact data returned (followers, following, likes, video count, bio, verification, region, avatar). The 'by handle' framing plus the field list clearly separates it from query-driven siblings like search_users and relation-list siblings like creator_followers.

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?

Gives a concrete decision context: 'qualify a partner or size up a competitor before committing,' which tells the agent when this lookup is worth making. It stops short of naming alternatives or exclusions (e.g., when to use search_users instead), so it is clear context without full routing guidance.

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