linkedin_get_profile

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

With no annotations provided, the description must disclose behavior. The verb 'Obtém' indicates a read operation, and the listed fields suggest a non-destructive retrieval. However, it does not mention authentication requirements, rate limits, or whether the data belongs to the authenticated user or someone else.

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?

A single sentence efficiently states the tool's purpose and lists the data categories, with no filler or redundancy.

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 tool with no parameters and no output schema, the description adequately explains what data is returned through the field list. It lacks an explicit statement that this is the authenticated user's profile, but that is a minor ambiguity given the absence of parameters.

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 tool has zero parameters and the schema has no properties, so schema coverage is trivially complete. The description correctly focuses on the output data rather than parameters, meeting the baseline for a no-parameter tool.

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 uses a specific verb ('Obtém') and resource ('perfil do LinkedIn'), and enumerates key data sections (headline, sobre, localização, experiências, formação, habilidades). This clearly distinguishes it from sibling tools that perform updates, adds, or searches.

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?

No explicit when-to-use or alternative guidance is provided. The context is implied by comparison with siblings (which are all mutation or search tools), but the description does not state 'use this for reading profile data' or mention exclusions.

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