List IITR AIS Features

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

Annotations already declare readOnlyHint=true, so the description's mention of 'Search' aligns. However, it adds minimal behavioral context beyond that, such as pagination behavior or data source specifics. The description does not contradict annotations, but does not significantly enrich 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?

The description is a single sentence, which is concise but lacks structure. It front-loads the purpose but omits important details that could be broken into multiple sentences for clarity.

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 7 parameters, no output schema, and many siblings, the description is insufficient. It does not describe return format, pagination behavior (limit/offset), or how to combine filters, leaving significant gaps for correct invocation.

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 description coverage is 0%, yet the description only covers 4 of 7 parameters (query, domain, role, mutating) but omits kind, limit, offset. It does not explain default values, allowed values, or parameter relationships, leaving agents to infer from parameter names alone.

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 verb 'Search' and identifies the resource as 'production-derived endpoint and screen catalog'. It lists specific filter criteria (text, API domain, portal role, mutation status), making the tool's purpose unambiguous and distinct from sibling tools like ais_get_feature or ais_get_portal_route.

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 implies usage for searching/filtering features but does not provide explicit guidance on when to choose this tool over siblings, nor does it mention exclusions or prerequisites. With many siblings, more context would help.

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