select_profiles

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

With no annotations, the description carries the full behavioral burden. It adds one useful constraint ('by exact name', implying no fuzzy matching), but says nothing about whether the selection replaces or appends to existing state, whether it is validated against the printer, or what happens on an invalid name.

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?

One sentence, front-loaded with the action and resources, and the parenthetical constraint lands at the end where it is easy to scan. No filler.

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 3-required-param tool with zero schema descriptions, no annotations, and no output schema, the description covers purpose and name format but leaves error handling and the source of valid names unspecified. Adequate but with clear gaps.

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 coverage is 0%, so the description must compensate: it names all three parameters (printer, print_profile, filaments) and specifies the exact-name format, which is meaningful. It still omits whether multiple filaments must be ordered, whether 'printer' is a profile name or a printer model, and cardinality rules.

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 ('Select') and names all three resources (printer, print, filament profiles), plus the downstream purpose ('to slice with'). It is distinguishable from siblings like save_profile_as or import_profile_bundle, though it doesn't explicitly contrast with list_compatible_profiles, which is the nearest discovery-oriented sibling.

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?

'to slice with' implies this is a pre-slicing configuration step, so the usage context is inferable. However, it never says where valid profile names come from (e.g., list_compatible_profiles) or what happens if a name is wrong, so no alternatives or exclusions are given.

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