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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context: the resource is 'owned' and 'private,' and the response will never contain encrypted input or provider credentials — useful security disclosure beyond the annotations.

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 tight sentences with the resource and scope stated first and the security guarantee second. The 'Private draft:' label adds a little noise but costs little.

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?

An output schema exists, so return-value explanation is not required, and annotations cover the safety profile. However, for a tool whose only parameter is undescribed and whose sibling set is crowded with similar invocation/operation tools, the description leaves the agent without enough to obtain a valid invocationId or rule out adjacent siblings.

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 0% and the single required parameter invocationId is never mentioned in the description. The word 'owned' hints at an access constraint, but there is no guidance on the identifier's format, where to obtain it, or what happens on a non-owned ID — the gap the description should have filled.

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 a concrete verb and resource: 'inspect an owned invocation intent and its approval state.' This clearly distinguishes retrieval of an intent's approval state from executing it (execute_provider_invocation) or reading provider operations (get_provider_operation). The 'Private draft:' prefix is ambiguous but doesn't obscure the core purpose.

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?

No statement of when to call this versus siblings like get_provider_operation, list_provider_access_requests, or prepare_provider_invocation. The approval-state mention weakly implies 'check before executing,' but no preconditions, alternatives, or exclusions are given.

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