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

Goes far beyond the sparse annotations (readOnlyHint=false, idempotentHint=false) by disclosing real-world stakes: it 'WRITES a real application under a real person's name and commits them to a 5-week in-person NDA-bound program.' It also reveals edge-case behavior (a second application is refused, not merged), the one-time-only claim_token display requirement, and the auth model (no auth required; token only attributes). This is deep behavioral disclosure with no annotation contradiction.

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?

Dense but every sentence earns its place: the highest-stakes warning (real commitment) is front-loaded, followed by the guardrail, prerequisite, duplicate-handling, and output-token warning. For a high-stakes 14-parameter write operation, the length is fully justified with zero redundancy.

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?

With no output schema present, the description supplies the exact return shape 'Returns: { ok, application_id, claim_token, status, failed_gates, cohort, message }' and explains how to handle the critical claim_token. It covers prerequisites, consequences, edge cases, and auth behavior, making it complete for an agent to invoke correctly.

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 100%, so the baseline is 3. The description adds value beyond the schema by flagging the nda_ack, commit_5_weeks, and in_person_sf parameters as 'promises they have to keep' that must be confirmed with the human, and by pointing to ic_spatial_beta_program for exact allowed values on enum-backed fields like profile and availability.

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: 'Submit an application to the 50-person spatial-computing beta.' The description clearly differentiates this from the sibling ic_spatial_beta_program by instructing the agent to call that tool first for the catalog, and the scope (applying versus status/program info) is unmistakable.

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 directs the agent to 'Call ic_spatial_beta_program first for the catalog and the exact allowed values,' giving a named prerequisite and alternative. It does not explicitly spell out when NOT to use ic_spatial_beta_status, though the apply-versus-check distinction is reasonably clear from naming and context.

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