manage_profile_hints

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

No annotations are provided, so the description must disclose behaviors. It explains the tool manages a cache for auto-switch middleware and gives an example of staleness. However, it does not detail side effects (e.g., impact on routing) or permissions needed. It provides moderate transparency.

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?

Two sentences: first explains what it does and the underlying data structure, second gives usage guidance. No wasted words, front-loaded with the most important information.

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 no output schema and moderate complexity (3 params, no nested objects), the description covers purpose, when to use, and basic parameter roles. It could mention error cases or what happens after clearing, but it is sufficiently complete for a cache management 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?

Input schema covers all three parameters with descriptions (100% coverage). The description adds value by explaining the 'resourceKey → profileName' mapping and the concept of hints, which goes beyond the schema.

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 inspects, sets, or clears profileHints, which is a specific cache. It explicitly names the resource (resourceKey → profileName cache) and the verb (inspect/set/clear). No sibling tool has a similar purpose, so it is well-differentiated.

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 gives a clear use case: 'Useful when a hint goes stale (e.g., a profile lost access to a doc).' It does not explicitly state when not to use or list alternatives, but the context is clear enough for agents to decide.

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