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

Annotations already cover the safety profile (readOnly=false, destructive=false, idempotent=false, openWorld=true); the description adds genuinely new behavior: no duplicate detection and that the new groupID is returned, plus the underlying endpoint. It does not mention permission/scope requirements, which is the main remaining gap.

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?

Four short clauses, front-loaded with the WRITE marker and the core action, then the duplicate caveat, the return value, and the endpoint. Every element adds signal with no padding.

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?

It covers what the tool does, the duplicate risk, and the return value, but for an 18-parameter mutation tool with thin schema coverage and no output schema, an agent still lacks guidance on which fields matter or how the address and custom-field blocks behave.

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 18 parameters and only 39% schema description coverage, the description carries a heavy compensation burden but says nothing about any parameter — not the required group_name, nor the mutually-implied address_type/street/city/state grouping, nor account_manager's id-or-name convention. This is a substantial gap.

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 specific verb and resource ('create a new group / employer business account in AgencyBloc'), disambiguates the domain term 'group', and implicitly distinguishes itself from read-side siblings by pointing at search. An agent knows exactly what object is being created.

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?

'It does not check for duplicates: search first' gives explicit pre-call guidance that routes the agent to agencybloc_search_groups. It lacks explicit when-not-to-use conditions or alternatives for attaching groups to policies, but the primary usage rule is stated.

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