get_schema

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

With no annotations, the description carries the burden of behavioral disclosure. It adds useful context ('Runs in your Kuudo deployment, not here') and implies a read-only schema retrieval, but it does not describe return format, error behavior, or potential side effects.

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 short and front-loaded with the core action. The three sentences each add some value, though 'Catalog entry' is slightly redundant with the tool's purpose.

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?

For a two-parameter schema-lookup tool with a complete input schema, the description is nearly sufficient. It explains the workflow position and the deployment context; no output schema exists, but the tool's return nature is implied by its name and 'get parameter schemas'.

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 100%, so the schema already documents both 'tools' and 'detail' thoroughly. The description adds only the ordering hint 'after searching' and does not meaningfully enrich parameter 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?

The description states a clear verb-resource pair: 'Get parameter schemas for specific tools,' which distinguishes it from search and execute. The opening phrase 'Catalog entry' is somewhat vague, but the main clause is unambiguous.

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 explicit usage context: use it after searching to obtain the detail needed to call a tool. It does not mention when not to use it or name alternative tools, but the placement in the workflow is clear.

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