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

Annotations declare readOnlyHint=true and destructiveHint=false, so the description doesn't need to restate that. It adds the prerequisite context, which is useful, but doesn't disclose any additional behavioral traits (e.g., whether it opens a session, requires external auth, or has side effects). Given annotations cover the safety profile, a 3 is appropriate—it adds some context but not deep behavioral detail.

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, clear sentence that is front-loaded with the action and immediately states the context. No filler or redundant phrasing.

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 tool with no parameters, no output schema, and annotations that already cover read-only safety, the description is complete. It tells the agent exactly when to use it (as a prerequisite) and which tools it supports. Nothing an agent needs to call it correctly is missing.

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?

There are no parameters, so schema coverage is effectively 100%. The baseline is 4 per the rubric, and the description doesn't need to add parameter info since none exist. It doesn't introduce any ambiguity.

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?

States a clear verb and resource ('Connect your Compteam account') and differentiates itself from siblings by framing it as a prerequisite for member, child, class, RSVP, and free-trial tools. It is not a tautology and gives enough specificity to distinguish it from the sibling tools, though it doesn't detail what 'connect' entails.

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?

Explicitly states when to use the tool: 'before using member, child, class, RSVP, or free-trial tools.' This provides clear context for usage, but it doesn't mention when not to use it or alternatives, which are not really applicable for a prerequisite action. The guidance is sufficient for an agent to decide to call it first.

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