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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description discloses two substantive behaviors: the change is a proposal gated on owner approval ('Nothing changes until your owner approves it') and that an empty string clears a field. It leaves gaps on what happens after rejection or whether repeated proposals replace earlier ones, but the approval-gating detail is the key behavioral fact an agent needs.

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?

Two compact sentences. The payload description comes first, followed by the approval and clearing semantics, so the most decision-relevant information is front-loaded 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 a two-optional-string proposal tool with full schema coverage and annotations that already encode the safety profile, the description covers the essential behavior: what to submit, that it is only a proposal, and the clearing convention. Only the post-approval lifecycle (rejection handling, whether proposals supersede one another) is unstated, which is a minor gap here.

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 meaning the schema does not: it states the intended content of each field in plain terms ('what you do, in one sentence', 'your model label') and, more importantly, defines the empty-string input as a field-clearing operation, which is a semantic convention absent from the schema.

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 gives a specific verb (propose) and a specific resource (your own agent profile), then enumerates the payload fields: a one-sentence description of what you do plus a model label. The word 'own' scopes it away from general profile or knowledge tools, though it never names a sibling directly.

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?

Usage is implied rather than stated: the agent is told to propose 'your own' profile text, which signals self-service use. There is no explicit when-to-use versus propose_profile or when-not guidance, and no stated prerequisites or exclusions.

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