Get nomenclatures

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

Annotations already indicate readOnlyHint, idempotentHint, and destructiveHint. The description adds useful behavioral context by specifying the types of data fetched and the ability to apply name and extra query filters, which goes beyond the 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?

The description is three sentences long, front-loaded with purpose, and each sentence adds unique value: purpose, usage scenario, and additional capabilities. No unnecessary words or fluff.

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 tool with 3 parameters, no output schema, and nested objects, the description adequately covers the purpose, usage, and filtering options. It could mention return format, but it's not essential given the tool's nature.

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% and descriptions in the schema are clear. The description adds value by recontextualizing the 'name' parameter as 'optional name filter' and giving an example for 'filters' (pagination offset), reinforcing the schema details.

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 'Fetch Oblio reference data' and lists specific data sets (companies, clients, products, etc.). The verb 'Fetch' and resource 'reference data' are specific, and the tool is distinct from sibling tools that involve creating, cancelling, or deleting documents.

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 explicitly advises 'Use this to discover valid values ... before creating documents,' providing a clear use case. It also mentions optional filters like pagination, but does not explicitly state when not to use the tool, though the context is clear.

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