linkedin_extract_topics

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

With no annotations, the description carries the full burden. It usefully discloses that the tool outputs topic names and mention frequencies and implies a read-only extraction. It does not explain what 'retrieved activity' means operationally, whether data is re-fetched, or what happens if no activity exists.

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 one concise sentence with no filler. It front-loads the core behavior and output, making it easy to scan and process.

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?

There is no output schema, so the description must clarify return format and usage pipeline, but it only gives a high-level summary. It omits preconditions such as 'activity must have been retrieved first' and provides no detail on the structure of the returned topics or frequencies.

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 only parameter, profileId, is already described as 'Profile ID to extract topics from'. The description adds no additional parameter semantics, so the baseline score of 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?

The description uses a specific verb ('Extracts') and names the resource ('top professional topics and mention frequencies') from 'retrieved activity'. It clearly distinguishes this from lead-ranking and prospecting siblings, though 'analyze_recent_activity' may overlap somewhat in 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?

The phrase 'from retrieved activity' implies a prerequisite, but the description never explicitly says to use this after retrieving activity or names alternatives. The agent is left to infer when this tool should be selected among 18 siblings.

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