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

Beyond the annotations (readOnly, idempotent, non-destructive), the description adds valuable behavioral details: login is required, the server has already reconciled data, canFill=true means the field is empty and claimable, the phone number is stripped from fields, and a missing bound phone returns organization_import_verified_phone_required rather than an empty list.

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?

The description is well-structured with labeled sections for login requirement, the combination workflow, and edge-case pitfalls. Every sentence carries meaningful information, and key caveats are front-loaded.

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?

Given zero parameters, read-only annotations, and no output schema, the description fully covers what an agent needs: what the tool returns, how to interpret canFill, the follow-up claim workflow, the error behavior for missing phone binding, and how to dismiss unwanted claims.

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?

The tool has zero parameters, so the baseline is 4. The description adds useful output semantics such as canFill=true and fieldKeys, even though there is nothing to explain about input parameters.

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 clearly states a specific verb and resource: listing organization profile data matched to the user's phone number that are awaiting claim. It distinguishes this from siblings by naming claim_organization_profile and dismiss_organization_claim, so an agent can tell it apart without opening schemas.

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 description provides explicit orchestration guidance: use this tool to fetch claimable fields, pass canFill=true items to the user for confirmation, then call claim_organization_profile with all fieldKeys. It also names dismiss_organization_claim for unwanted items, giving clear context for when to use this tool versus the adjacent claim/dismiss tools.

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