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

No annotations are supplied, so the description carries the full burden of behavioral disclosure. It does clarify the important identity aspect (the post is attributed to the authenticated member), but for a mutation it omits whether the action is reversible, what permissions/scopes are required, rate limits, and what the response contains (e.g., a post URN).

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 front-loaded sentence with no filler or redundancy. It is efficient, though its brevity is part of why key details like visibility semantics are missing.

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 write operation with no annotations, no output schema, and undocumented parameters, the description is thin. An agent still lacks the visibility enum meaning, permission requirements, and what a successful call returns, all of which matter for a publishing action.

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?

With 0% schema description coverage across 2 parameters, the description must compensate. 'Text post' loosely signals that the required text field is the body content, but nothing explains the visibility enum values PUBLIC vs CONNECTIONS or the PUBLIC default — the one parameter where an agent is most likely to make a wrong choice.

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 gives a specific verb ('Publish') and resource ('a text post') scoped to 'the authenticated member's LinkedIn feed', which tells an agent exactly what gets created and under whose identity. It does not name or differentiate from the only sibling, get_profile, but the two are functionally distinct enough that confusion is unlikely.

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?

Usage is implied by 'Publish ... to the feed' — this is the tool for creating a post rather than reading profile data. There is no explicit when-to-use/when-not-to-use statement, no mention of prerequisites such as granted scopes, and no guidance on choosing between visibility options.

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

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

No annotations are supplied, so the description carries the full behavioral burden. 'Get' implies a non-mutating read and 'authenticated member's' hints at an OAuth requirement, but the description never states that it is read-only, what happens when the token is missing or expired, or whether results are cached. It also does not describe the return shape beyond a field list.

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 front-loaded sentence with the resource and returned fields up front and no filler wording. Nothing could be removed without losing information.

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 zero-parameter tool with no annotations and no output schema, the description covers the essentials, and the enumerated field list partially compensates for the absent output schema. The remaining gap is failure behavior when no authenticated session exists, which an agent may need to handle.

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 takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The parenthetical field list is a small bonus that tells the agent what the call yields, though it is really return-value information rather than parameter meaning.

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?

Specific verb ('Get') plus a precisely scoped resource ('the authenticated member's basic LinkedIn profile'), and it enumerates the returned fields (name, email, picture, locale). The 'authenticated member's' phrasing also disambiguates scope. It does not explicitly name a sibling, but with only create_post alongside it, the read/write distinction is self-evident.

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?

Usage is only implied: an agent can infer this is the tool to call to identify the current user, and there is no alternative read tool to choose between. There is no explicit statement of when to use it, no precondition (e.g. requires a valid access token), and no note about what to do on failure.

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