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

With only openWorldHint=false and destructiveHint=false in annotations, the description carries the behavioral load and does so well: it distinguishes data written directly (group/event record and roster rows for existing people) from data staged for member acceptance (person changes and new people), and notes non-attending guests are skipped. It omits idempotency/upsert conflict behavior and permission requirements.

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?

Three dense sentences that front-load the core purpose, then the write-vs-stage split, then the skip rule and limit. Every sentence adds distinct information with no filler.

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 complex 7-parameter nested import tool, the description gives a solid conceptual model of what gets written versus staged and the batch limit. However, with 29% schema coverage it leaves the agent without guidance on required inputs like companyId/source, making it only minimally sufficient to invoke correctly without opening the schema.

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 only 29% across 7 nested parameters, so the description would need to compensate—yet it explains almost no parameter semantics. It only mirrors the 500-person maxItems cap on 'people'; companyId, source, connectionId, meta, and the many person fields are left undocumented by both schema and description.

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 names a specific verb+resource+scope: the entry point for a connector or import batch carrying an optional group/event roster plus people. It is clearly distinguishable from single-record staging tools like fundraising_stage_network_person, though it never names those siblings explicitly.

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 entry point for a connector or import batch' implies when to use it—bulk imports rather than one-off writes—but the description never states when NOT to use it or names an alternative tool for smaller/interactive cases. The 500-person cap is a constraint, not usage guidance.

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