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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description reinforces this with the strong downstream warning against overwriting connector-discovered schemas, which is real behavioral context the annotations don't carry. It does not spell out the returned structure beyond the access-mode tokens, keeping it short of a 5.

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 sentences, front-loaded with the classification purpose before the rationale. The second sentence is dense but every clause carries meaning (the two destructive mistakes it prevents), so there is no padding.

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 single-parameter, read-only classification tool with no output schema, the description supplies both the dimensions being classified and the enum of access modes, which is the essential return information. A brief note on whether it lists all schemas or only bound ones would close the remaining gap.

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?

With only one optional parameter at 100% schema description coverage, the schema already explains that project_uuid defaults to the key's project. The description's phrase 'this project's schemas' is consistent with that default but adds no new semantics; 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?

The description gives a specific verb ('Classify') plus the exact resource ('this project's schemas') and enumerates the two classification dimensions returned: connector-backed vs app-authored, and access mode with its four values. That is enough to distinguish it from the schema_* siblings, though no sibling is named explicitly.

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 states the decision this tool enables ('Use it so you DON'T render create/edit UI for read-only live sources... or regenerate/overwrite connector-discovered schemas'), which is concrete when-to-use context. What is missing is an explicit contrast with the closest alternatives (schema_list_project, build_list_data_sources), so the agent must infer which list tool to call.

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