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

Beyond the annotations, it discloses important operational consequences: changing name, intro, type, agreement, or form advances the agreement version; changing name or type resets certification to pending review; official/alliance fields are locked; and changes are visible to all members and should be confirmed with the user first.

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 dense but well structured with bracketed sections and front-loads the permission requirement, field list, workflow, and cautions. Every sentence carries actionable 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 an 8-parameter mutation tool with nested objects, enums, no output schema, and rich annotations, the description is complete enough: it covers permissions, patch behavior, side effects, locked cases, and user-confirmation requirements.

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, but the description adds useful meaning by grouping fields by permission level (owner-only fields include visibility, joinPolicy, and terms) and by stating patch semantics: only pass the fields you want to change.

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 states a specific verb and resource: updating organization profile fields, enumerating name, intro, type, form questions, visibility, join policy, and agreement. It explicitly distinguishes itself from get_organization and set_organization_logo, so an agent can identify its scope without opening sibling 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?

It gives an explicit workflow: read current state with get_organization, then call this tool, and use set_organization_logo for logos. It also states the required permission level (OWNER/ADMIN), notes that only fields being changed should be passed, and describes locked fields for official entries and alliances.

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