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

Annotations already establish that the tool is read-only, idempotent, and non-destructive. The description adds behavioral value beyond these by describing what returned entries contain, how 'schema' maps to create_project, and what 'tables' notes indicate about authorization.

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 and usage guidance, and each major section—template list, schema format principles, and create_project integration—earns its place. It is slightly dense with formatting emphasis, and the closing TIP partially reinforces earlier guidance, but overall it remains efficient.

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 zero-parameter, read-only tool with no output schema, the description is complete: it lists available templates, explains the schema format expectations, and tells the agent how the output should be consumed by create_project. No critical decision or next step is left unexplained.

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?

The input schema has zero parameters, so the baseline is 4 and there is no parameter ambiguity to resolve. The description appropriately focuses on output content and usage rather than parameter details.

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 opens with a specific verb-object statement: 'Get pre-built template schemas for common use cases.' It further distinguishes the tool by positioning it as the first stop when creating a new project and enumerating concrete template names, so an agent can differentiate it from generic schema retrieval tools.

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 provides explicit usage context: 'USE THIS FIRST when creating a new project!' and advises studying templates before creating custom schemas. It does not explicitly state when not to use this tool or compare it to similar siblings, but the guidance is clear and actionable.

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