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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description does add real value beyond that by stating the returned data is limited to metadata/approved fields with no secrets, contacts, or original files, but it says nothing about authorisation requirements, what 'workflow state' actually contains, or failure behaviour for an unauthorised or unknown target.

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 short sentences with no filler, and the core operation is front-loaded before the data-scope caveat. Every clause contributes information.

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 is the only guide to return values, and it gives just a partial sense ('metadata/approved fields') without indicating shape or what workflow states exist. Combined with the unexplained required parameters, it is adequate but leaves meaningful gaps for an agent trying to call it correctly.

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%, so the description must carry the burden and it does not: neither parameter is mentioned. It is unclear whether targetId refers to a credential, an application, or a flow instance, and flowType's APPLICATION/RENEWAL distinction is only implicit in the enum rather than explained in prose.

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: reading 'credential workflow state', scoped to authorised data and metadata/approved fields. That is clearly distinguishable from generic reads, but it never differentiates itself from near-neighbours such as get_credential_details, get_flow_template, or get_flow_field_catalog, which an agent could easily confuse it with.

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 statement of when to use this tool versus the many credential- and flow-related siblings, and no prerequisites or alternatives are named. The only guidance-like content is a data-scope disclosure ('metadata/approved fields only'), which describes what comes back rather than when to call it.

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