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

No annotations are provided, and the description fails to disclose any behavioral traits beyond billing. It doesn't state whether the tool makes a network request, handles errors, or what the output looks like. The billing note is useful but insufficient; the description does not contradict annotations (since none exist), but it leaves the agent with no expectations about side effects or data format.

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?

This is a single sentence that is redundant: 'Get social network metrics By username Group: Profile. Billing per call: 1 Credits.' The first part repeats the tool name, and the second is a billing note. It is short, but it fails to convey the essential structure. The 'Group: Profile' hint is slightly helpful, but it's not enough to warrant a higher score.

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?

Given the complexity of the tool (likely returning a nested structure of social network metrics) and the absence of an output schema, the description provides no behavioral context. The tool has a single parameter, but with no description, the schema lacks any parameter semantics or output schema, the description is incomplete. The tool's output is a simple but no guidance on the schema's coverage is 0%. The tool has a description that returns a social matrix with no parameters, but the coverage is low.

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%, and the description only mentions 'By username' without explaining the format, constraints, or what the username should be (e.g., LinkedIn profile ID, URL, or LinkedIn URN). The schema provides the parameter 'username' but the description doesn't clarify if the username is an ID or slug. The single parameter is described as 'social matrix' which is a metric, but the description lacks any semantic meaning. The description does not add value beyond the schema field, and the schema provides a valid example, but no param semantics are needed.

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 is minimal and just states the tool gets social matrix metrics by username. It conveys the verb "Get" plus the resource "social matrix". However, the description is unclear about what data the social matrix actually contains, making it hard to distinguish from other profile-related tools like get_api_v1_profile_overview or get_api_v1_profile_details.

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 the many sibling profile tools. It doesn't mention whether this is for LinkedIn profile data, social network metrics, or if it requires a username that is a valid LinkedIn profile. With 47 sibling tools, the absence of usage context leaves the agent guessing.

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