modeling_best_practices

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

No annotations are present, so the description fully bears the responsibility. It describes the tool as a query that 'gets best practices' and returns them, which is non-destructive. However, it does not disclose any behavioral traits such as rate limits, authentication needs, or side effects beyond the obvious read operation.

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 very concise and well-structured with a bullet list, clear Args/Returns sections, and no redundant text. Every sentence adds value.

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?

Given the tool has only one string parameter and no output schema, the description is nearly complete. It explains what the tool does, what to provide, and what to expect back. Minor improvement could be made by specifying that category values are case-sensitive or must match exactly.

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 0%, so the description must compensate. It lists five valid category values with a one-line explanation each, adding meaning beyond the bare schema. However, it does not explicitly state that these are the exact allowed string values or specify case sensitivity.

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's purpose: 'Get best practices for different modeling categories.' It lists five specific categories with brief explanations, distinguishing it from sibling tools as the only one dedicated to best practices.

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?

No explicit guidance on when to use this tool versus alternatives is provided. Usage is implied by the tool's unique purpose, but the description does not mention when-not-to-use or suggest alternatives.

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