preset_get_hint

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

The annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds value by enumerating the valid contexts for the hint, but it does not disclose what the hint returns, how invalid contexts are handled, or any other behavioral 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 one compact, front-loaded line with no filler words. Every word contributes to defining the parameter's allowed scope, so it earns full marks for conciseness even though it under-specifies the tool's purpose.

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 parameter and no output schema, the description should at least state that it returns an AI hint and ideally what kind of hint. It only lists contexts, leaving the return value, default behavior, and meaning of each context unexplained. This is too incomplete for an agent to confidently use the tool.

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 schema's only parameter 'context' has no description, default, or enum, and schema coverage is 0%. The description compensates by listing the meaningful context values: modeling, texturing, rigging, and export. It does not fully explain nuances, but for a single simple parameter this is a solid contribution.

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 only lists context values ('modeling, texturing, rigging, export') without stating what the tool does. The action of retrieving or showing a hint must be inferred from the tool name and the annotation title 'Get AI Hint', so the description itself lacks a clear verb and resource.

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 guidance is given about when to use this tool versus related sibling tools like preset_apply or preset_list. There are no usage conditions, prerequisites, or exclusions, so an agent gets no help deciding between alternatives.

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