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 still adds real value beyond that: access is permission-scoped ('authorised'), and the payload explicitly excludes secrets, contacts and original files, which tells the agent what it will never receive. It stops short of describing return shape or pagination behavior, which keeps it from a 5.

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 sentences, front-loaded with the operation and followed by the data-scope caveat; nothing is padded. The phrase 'through the existing application' is the one bit of low-information 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 paginated list tool with no output schema and zero parameter documentation, the description should say what a catalog entry looks like, how paging works (default 50, max 100, offset cap 25000), and what query searches. None of that is present, so an agent must open the schema and still guess at the return shape.

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 none of the three parameters (limit, query, offset) is mentioned in the description. limit/offset are conventional enough to infer, but 'query' is undefined – nothing says which fields it matches or whether it is a prefix or full-text search – so the description does not compensate for the schema 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 a verb (Read) and a resource (flow field catalog), but 'flow field catalog' is unexplained jargon and the description never distinguishes it from near siblings such as get_field_layout, list_custom_field_definitions, or list_flow_content_templates. An agent knows roughly the shape of the operation but not precisely what object it returns.

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 when-to-use guidance, no prerequisite, and no named alternative. 'Through the existing application' and 'Metadata/approved fields only' read as scope constraints rather than selection criteria, so an agent has no basis for choosing this over get_field_layout or list_custom_field_definitions.

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