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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description adds useful content detail — that changes include edits made by Google or the public and carry old/new values — but says nothing about ordering, default limit, or pagination behavior.

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?

One tight sentence with no filler, and the resource definition is front-loaded. It is slightly dense but every clause carries information about what is returned.

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, the description does a reasonable job of describing returned content (old and new values, edit history). However, for a tool with three filter parameters and an undocumented limit, it leaves an agent without enough to invoke it confidently beyond the required id.

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 only 33%, and the description mentions no parameters at all. The required profile_id is never referenced, the limit parameter has no description anywhere, and the status filtering semantics (pending/accepted/reverted) are only partially captured by the schema example. The description does not compensate for the coverage gap.

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?

States the specific resource — changes detected on a Google profile via Profile Guard, including edit history with old and new values. The verb is only implied by the title ('List'), but the content scope is precise enough to separate it from siblings like sync_profile or request_profile_change_decision.

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?

There is no guidance on when to use this versus alternatives — notably request_profile_change_decision, which is the action counterpart for the same Profile Guard data. The description explains what data comes back but never states when a caller should reach for this tool or what conditions exclude it.

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