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

With no annotations provided, the description carries the full burden of behavioral disclosure. It tells the agent that the tool returns install snippet plus instructions, and that it returns create-one-first instructions when no pixel exists, which is a meaningful edge-case behavior. It does not explicitly state the read-only nature, but this is strongly implied by 'get' and the nature of the tool.

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 zero filler. It front-loads the primary purpose and resource, then immediately gives usage context and the edge-case behavior. Every word adds 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?

For a zero-parameter, no-output-schema tool, the description covers the essential aspects: what it does, when to use it, and behavior when no pixel exists. It could have been slightly more explicit about the structure of the returned instructions, but the information needed to invoke the tool correctly is present.

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 has 0 parameters, so the baseline score is 4. The description correctly avoids mentioning parameters since there are none. No additional parameter-level explanation is needed because there is nothing to explain.

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 a specific verb 'Get' and a concrete resource: 'the user's SociaHive Pixel install snippet + instructions'. It also explicitly ties the tool to common user intents ('install the pixel' / 'track events on my site'), making it easy to distinguish from any sibling tools that might handle related but different tasks.

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 gives explicit when-to-use guidance via the quoted phrases 'install the pixel' and 'track events on my site'. It does not mention when not to use it or name alternative tools, but the provided context is sufficiently clear for an agent to decide when to invoke this tool.

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