scrapeer_get_block_catalog

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is known. The description adds behavioral context by stating the tool returns block type strings and custom-field schemas, and that guessing these leads to validation failures—clarifying the tool's role as a catalog. It doesn't cover return format details, but that's not expected given no output schema and the simple listing nature.

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?

The description is well-structured and front-loaded with the core purpose, followed by clear usage directives and an exclusion. Every sentence adds value: the purpose, the when-to-use, the mandatory call order, and the do-not-use alternative. No wasted words despite the guidance style.

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 zero-parameter tool with no output schema, the description is complete. It explains the result (block types and schemas), the context (before flow creation/update), and explicitly lists related sibling tools to use instead. The guidance about validation failures underscores its importance in the overall flow workflow.

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?

The tool has zero parameters and the schema coverage is 100%, so there is nothing to explain. Baseline for 0 params is 4, and the description appropriately doesn't add parameter info since none exist.

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: 'List the block types available for use in flows, with their custom-field schemas.' It clearly distinguishes this tool from siblings by explicitly saying 'DO NOT USE: to read an existing flow's blocks (use scrapeer_get_flow)', which sets it apart from the flow-reading tool.

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?

The description provides explicit when-to-use guidance: 'USE THIS TOOL WHEN: you are about to create or modify a flow...' and 'ALWAYS call this BEFORE scrapeer_create_flow, scrapeer_update_flow, or scrapeer_patch_flow.' It also gives an explicit when-not-to-use with an alternative: 'DO NOT USE: to read an existing flow's blocks (use scrapeer_get_flow).' This fully covers usage context and alternatives.

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