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

readOnlyHint already declares this is a safe read. The description adds genuinely useful context beyond that: the response is the raw JSON 'as-is' (important since no output schema exists) and app_id silently falls back to the configured KNACK_APPLICATION_ID. It does not mention rate limits or error behavior, but for a passive GET this is solid.

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?

Three compact sentences; the resource and its contents come first, then the endpoint, then the default-behavior note. No filler and nothing important buried.

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 carries the burden of describing the return value and does so ('full schema/metadata — objects, fields, scenes', raw JSON as-is). Combined with 100% parameter coverage and a read-only annotation, an agent has everything needed 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 100% and the single optional parameter is fully documented in the schema. The description's note that app_id defaults to KNACK_APPLICATION_ID largely restates the schema, adding no format or validation detail. Baseline 3 applies.

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 specific verb ('Fetch') and resource ('a Knack application's full schema/metadata') and enumerates contents (objects/tables, fields, scenes). The inclusion of the underlying endpoint GET /applications/{app_id} pins down exactly which resource is retrieved, distinguishing it from the record- and field-level siblings.

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 implies when to use it (when you need the whole schema at once) by stating it returns objects, fields and scenes together, but it never explicitly contrasts this with knack_list_objects or knack_list_fields, which are the obvious alternatives. Usage is inferable rather than stated.

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