pine_social_share

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

No annotations are provided, so the description carries full burden. It indicates mutation ('share on social media') but does not disclose side effects, authentication needs, rate limits, or what happens upon sharing. The behavioral disclosure is minimal.

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 two sentences with a clear arg list, no redundancy. It presents the purpose upfront and then lists parameters efficiently. Every sentence contributes value.

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 tool's simplicity (3 required params, output schema exists), the description covers the essential purpose and parameters. However, it misses contextual information such as authentication requirements or the need for a completed session. An output schema exists, so return value explanation is optional.

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%, so the description must compensate. It provides brief descriptions for each parameter: session_id as 'The completed session', platform with enumerated options, shared_url as 'URL of the social media post'. This adds meaning but lacks detail on formats or constraints.

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 tool's action: 'Share completed task results on social media to earn Pine credits.' It identifies the specific verb ('Share'), resource ('completed task results on social media'), and immediate benefit ('earn Pine credits'). This distinguishes it from sibling tools focused on authentication, sessions, and attachments.

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 description implies usage after completing a session (via the 'session_id' parameter) but does not explicitly state when to use or avoid this tool, nor does it mention alternatives or prerequisites. Guidance is only implicit.

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