get_default_profiles

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It clarifies the source of profiles ('built-in factory and community profiles that ship with the machine'), which adds context, but it doesn't describe return format, read-only nature, or any potential side effects. For a simple getter, this is minimally adequate but lacks richer detail.

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: the first states the core purpose, the second adds a practical use case. Every word earns its place, and the content is front-loaded with the action and resource. No filler or redundancy.

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 zero parameters and no annotations, the description must stand alone. It conveys what is returned (default profiles), and the use case ('starting points for recipe creation') helps the agent decide when to invoke it. While it doesn't explicitly state the return structure, the tool name and siblings give enough context for this simple getter.

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 properties, and the instruction baseline for 0 parameters is 4. Since there are no parameters to describe, the description doesn't need to add parameter-specific detail. The description correctly focuses on the resource being fetched.

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 retrieves 'built-in factory profiles and community profiles that ship with the machine,' using the specific verb 'Get' and a clear resource. This distinguishes it from sibling tools like get_all_profiles or get_profile by specifying that it returns only default/built-in profiles.

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 explains that these profiles are 'good starting points for recipe creation or modification,' giving a clear use case. It doesn't explicitly state exclusions or alternatives, but the context implies when this tool is appropriate compared to listing all profiles or fetching a specific profile.

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