kiota_info

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

No annotations are provided, so the description carries the full burden. The word 'query' suggests a read-only operation, and the description discloses the scope (languages, capabilities, dependencies), but it does not explain return format, how optional parameters affect results, or any operational behavior like network access or input validation.

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, well-structured sentence with no filler. It front-loads the action ('Query') and immediately specifies the resource, making it easy to parse.

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?

This is a simple query tool with no output schema and no annotations. The description is sufficient for a basic understanding, but it omits details about the return structure and how optional parameters alter the response, which could be important for an agent deciding how to invoke and interpret the results.

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 descriptions offer 100% coverage, documenting all three parameters (json, language, descriptionPath) with types, defaults, and enums. The description adds slight context by mentioning 'languages' and 'dependencies', which maps to the language parameter, but it does not add significant meaning 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?

Description uses a specific verb ('Query') and resource ('information about supported languages, their capabilities, and required dependencies for an API'). This clearly distinguishes it from siblings like kiota_search (searching) and kiota_client_* (client lifecycle operations).

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 retrieving language/dependency information but provides no explicit when-to-use guidance or mention of alternatives. No exclusions or prerequisites are stated, so the agent must infer when this tool is appropriate.

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