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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds useful behavioral context beyond annotations: web and mobile have different references, platform='mobile' changes behavior, and widget-type topics return full syntax. It does not cover auth, rate limits, or pagination.

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 front-loaded with the core purpose, then efficiently lists topic semantics and platform behavior. Every sentence adds actionable information, and the structure makes it easy for an agent to decide what topic to request.

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 documentation-retrieval tool with no output schema, the description is complete enough to invoke correctly. It explains topic values, platform behavior, and when to use the reference, leaving no critical gap for an agent preparing to write app or screen JSON.

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?

Although schema coverage is 100%, the description substantially enriches parameter meaning. It explains that topic='index' lists guides and widgets, enumerates guide categories, clarifies that any widget type name returns syntax, and explains the platform parameter's mobile/web distinction beyond the enum labels.

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: 'Read Fieldproxy's app-building reference.' It clearly distinguishes what the tool does from sibling tools by focusing on app-building guides and widget syntax, and it explains the main lookup modes (index, guides, widget types).

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?

It gives clear when-to-use guidance: read the relevant doc before writing any app or screen JSON, and it notes that docs are more reliable than memory. It also explains platform selection for mobile vs web. However, it does not explicitly state when not to use the tool or name alternative documentation tools.

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