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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral trait — a cost of '30 points per call' — but says nothing about failure modes, auth, or rate limits beyond cost.

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?

Front-loads the purpose in one English sentence plus a parallel Korean sentence, with the cost tagged at the end. Efficient overall, though the bilingual duplication conveys the same content twice.

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 single-parameter lookup with full schema coverage and no output schema, the definition is essentially complete: it names the source, the input form, the returned fields, and the call cost. Only usage routing to sibling tools is absent.

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 there is a single required 'url' parameter with its own example in the schema. The description only confirms it operates 'by URL' and adds no syntax or format detail beyond the schema, 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 — retrieves a LinkedIn public profile by URL — and enumerates the returned fields (name, position, experience, education, followers, connections, recent posts). This is clear and concrete, though it does not explicitly name its closest siblings (linkedin_company, linkedin_job) to differentiate scope.

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?

There is no when-to-use or when-not-to-use guidance and no mention of alternatives, despite several near-neighbors (linkedin_company, linkedin_job, other *_profile tools). The URL requirement is conveyed only implicitly via the schema, not as usage direction.

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