get_component_summary

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

With no annotations, the description carries the full burden. It discloses that the tool reads from local cache, makes no API calls, and resolves nested component references in a specific format. It doesn't explicitly state whether it's read-only or what happens on missing cache, but 'No API calls' and 'from local cache' strongly imply a non-mutating operation, which is meaningful behavioral context.

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 two sentences, front-loaded with the core purpose, then adds relevant details about output format and caching. Every clause earns its place; there is no redundancy or 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?

Given no output schema, the description compensates by outlining what the summary includes (widget tree, actions, params) and the nested reference format. It covers the key operational context (local cache, sync prerequisite). Minor omissions like error behavior are not critical for this simple read-from-cache tool, so it is nearly complete.

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 100% and each parameter already has a clear description (e.g., componentId and componentName with usage notes). The tool description does not introduce new parameter-level meaning beyond what the schema provides, so it meets the baseline for well-documented parameters but adds no extra semantic value.

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 opens with 'Get a readable summary of a FlutterFlow component from local cache' – a specific verb, resource, and source. It clearly distinguishes from siblings by targeting components (not pages), and lists summary contents (widget tree, actions, params). This provides an unambiguous 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?

The description states the prerequisite explicitly: 'Run sync_project first if not cached.' It also sets expectations by noting 'No API calls' and that data comes from local cache. While it doesn't name alternative tools like get_page_summary, the context clearly implies component-specific use, and the prerequisite guidance is actionable.

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