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

With no annotations to lean on, the description carries the full burden and does: it discloses the return values (tenantId, apiKey bearer token), the anonymous-until-claimed lifecycle, and a real destructive consequence — replacing an already-claimed account's credential 'loses its identity and history'. That is the kind of side-effect warning an agent cannot infer from the schema.

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?

Front-loads purpose, then the trigger, then the side-effect warning. Five sentences is on the long side, but nearly every clause carries operational weight (auth precondition, sibling routing, claim-link lifecycle, credential-replacement warning), so little is wasted.

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?

No output schema exists, and the description compensates by describing the response (tenantId, bearer token, claim link in response text). Auth preconditions, optional-parameter policy, and lifecycle consequences are all covered — nothing an agent needs to invoke this 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?

Schema coverage is 100%, so the baseline is 3, but the description adds a genuine usage constraint the schema does not: 'All arguments are optional; pass utm_source, utm_medium and utm_campaign, and invite, only if your human gave you them.' That governs when to supply them rather than just their format.

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?

Opens with a specific verb+resource+scope: 'Instantly provision a new anonymous Codemind account on the free plan — no credential, no human step required.' An agent can distinguish this account-provisioning tool from the surrounding build/review/test siblings immediately.

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?

States exactly when to call it ('build_feature ... fails with an auth error and no CODEMIND_API_KEY is configured') and names the alternative plus its trigger ('if you ALREADY have a configured apiKey, call get_usage_guide with topic "auth" before calling this tool again'). When-to-use, when-not-to-use, and the sibling alternative are all explicit.

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