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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds value beyond that by scoping results to the authenticated tenant and explaining what a schema is and how its id is consumed by create_datafile, which is genuine behavioral context an agent would otherwise have to infer.

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?

Two short sentences with no filler; the scope constraint and the domain definition are both front-loaded and every clause carries information the agent needs.

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?

Output schema exists, so return values need no explanation, and pagination parameters are fully documented in the schema. Combined with the tenant scoping and the cross-reference to create_datafile, the description leaves nothing an agent needs in order 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 all three parameters (page_size, page_token, slug_prefix) are documented there. The description adds no parameter-level meaning such as ordering, default page size, or slug semantics, so the baseline of 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 and resource ('List the schemas') plus scope ('belonging to the authenticated tenant'), which is more precise than the bare title. It does not explicitly distinguish itself from get_schema or create_schema, but the list-vs-single split is inferable from the name and the sibling set.

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?

Use case is implied by the sentence about referencing a schema_id when creating a datafile, which hints at discovery-before-create. However, there is no explicit when-to-use/when-not guidance and no named alternative such as get_schema for fetching a known schema by id.

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