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

The annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds the behavioral detail that results are scoped to the authenticated tenant, which is not in the annotations. It also hints at the relationship to datafile creation, going beyond the bare annotation metadata.

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 with no redundant wording. It front-loads the primary action (list schemas for tenant) and then adds useful context about schema purpose and usage, all without unnecessary detail.

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 a defined output schema (though not shown in the snippet) and a clear description of the operation's purpose and scope, the description is complete for a list operation. It does not need to explain return values because the output schema is expected to convey that information.

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% for the three parameters (page_size, page_token, slug_prefix), each with a clear description. The tool description does not add extra meaning beyond the parameter descriptions, so it meets the baseline for high coverage but does not exceed it.

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 clearly states the tool lists schemas for the authenticated tenant, distinguishing it from other list tools by specifying the resource type and tenant scope. It also provides context about schemas being JSON Schemas for datafiles, which helps an agent understand the 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 gives context on when schemas are relevant (referenced when creating a datafile), but does not explicitly mention when to use this tool versus alternatives like list_datafiles. However, the clarity of the resource type and tenant scope provides adequate guidance for typical usage.

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