axint.suggest

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

Annotations already mark readOnlyHint and idempotentHint. Description adds behavioral context: local mode is read-only and offline, Pro mode may call Axint endpoint with credentials, domain is a weak hint. No contradictions with annotations.

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?

Fairly concise with clear structure: purpose, then usage guidance, then behavioral notes. Some repetition ('use this to discover... Use: use before generation') could be tightened, but overall well-organized.

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's complexity (10 parameters, output schema exists), the description covers purpose, usage guidelines, behavioral notes, and parameter hints. Output schema provides return structure, so description does not need to detail that. Complete enough for an agent to decide when to call and what to expect.

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 100% so baseline is 3. Description adds value by clarifying that 'domain is only a weak hint' and that local mode does not use network, supplementing the schema descriptions. However, some schema descriptions (e.g., mode) are truncated, so the description helps marginally.

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?

Clearly states the verb 'suggest' and resource 'Apple-native features' based on app description. Differentiates from sibling tools like axint.feature and axint.registry.search by explicitly stating usage before generation and not a substitute for registry search.

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?

Provides explicit guidance: 'Use this to discover what Axint can generate for an app before calling axint.feature' and 'not a substitute for registry search or validation'. Clearly states when to use and when not to, with alternatives.

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