get_profile_highlights

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

With no annotations, the description must disclose behavior. It indicates a read operation but lacks details on authentication, rate limits, side effects, or the nature of the returned data. The 'limit' parameter implies pagination, but this is not explained.

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 a single short sentence, which is concise but lacks necessary detail. It is not verbose, but the brevity comes at the cost of omitting parameter semantics and usage guidance.

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 two parameters and existence of an output schema, the description fails to provide enough context. It does not explain the meaning of highlight folders, how to use the parameters, or what the output contains, making it incomplete for an agent to use correctly.

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 0% and the tool description does not explain any parameter. 'target' and 'limit' are not described at all, so the agent has no understanding of what values to provide or the effect of 'limit' (default 0).

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 ('List') and resource ('highlight folders'), making the purpose clear. It distinguishes from sibling 'download_profile_highlights' which implies an alternative action, but does not differentiate from other 'get_profile_*' tools that also list items, leaving some ambiguity.

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 guidance is provided on when to use this tool versus alternatives. The description does not mention prerequisites, common use cases, or exclusions, leaving the agent with no context to decide between this and similar tools like 'get_profile_stories'.

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