axint.suggest

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

Describes effects beyond annotations: local mode is read-only, Pro mode may call an endpoint. This adds behavioral context to the readOnlyHint and idempotentHint annotations. No contradiction 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?

Concise with front-loaded purpose, followed by usage and behavioral details. No extraneous information; every sentence adds value.

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?

Complete coverage given complexity: explains what it does, when to use, behavioral modes, parameter hints, and output structure implied. Output schema exists, so return values need not be detailed.

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 covers 100% of parameters with descriptions. The tool description adds overarching context about parameter weighting (domain vs app description) and mode effects, which adds value 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 it suggests Apple-native features based on app description, distinguishing it from siblings like registry search or validation. It specifies the verb 'suggest' and the resource 'Apple-native features'.

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?

Explicitly states when to use ('before generation to choose Apple surfaces') and when not to use ('not a substitute for registry search or validation'). Also provides parameter weighting guidance ('domain is only a weak hint; the app description wins').

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