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

Annotations already declare readOnlyHint: true and openWorldHint: true, so the description does not need to repeat that it is read-only. However, the description adds no behavioral context beyond the bare function—it does not mention that the profile data is public, what fields are returned, or any edge cases like handle not found. With annotations covering the safety profile, the description should ideally add more, but it remains silent.

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 only two short sentences: 'Get a Threads profile for a creator or account. Accepts a handle.' It is concise and front-loaded with the main action. The second sentence about accepting a handle is redundant with the schema but does not significantly waste space. It earns its place by being clear, though it could have been combined into one 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 simple read-only operation with one parameter and no output schema, the description is minimal but functional. However, it does not mention what the response contains (e.g., profile details like username, bio, follower count) or handle edge cases. Since there is no output schema, the description should provide some hint about the returned data structure. The current description is adequate but incomplete for an agent to know what to expect.

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 description for 'handle' already fully explains the parameter ('Threads handle to look up, with or without a leading @'), covering 100% of the parameter semantics. The description says 'Accepts a handle,' which adds no new meaning. Since schema coverage is high, the baseline of 3 applies, and the description does not provide any bonus information about parameter usage or constraints.

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 action (Get) and resource (Threads profile), specifying it applies to a creator or account and accepts a handle. This is specific enough to differentiate from other profile_get tools on different platforms, though it does not explicitly distinguish from related Threads tools like threads_profile_posts_list. The verb and resource are precise, so it meets most criteria for a 5 but lacks explicit sibling differentiation.

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 provides no guidance on when to use this tool versus alternatives. It does not mention that this should be used for profile information vs. posts or search, nor does it note any conditions like needing a handle. This is a simple tool, but with many sibling profile tools, some explicit usage context would help. There is no exclusions or alternative routing.

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