get_instance

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

With no annotations, the description fully discloses behavior: supports pagination (limit, offset), case-sensitive search, all_instances flag, detailed mode, and returns JSON with metadata. No contradictions; it's a read-only tool, and all filtering modes are explained.

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?

Well-structured with sections: summary, functions, usage, args, returns, examples. Front-loaded with purpose. Slightly verbose but justified by the number of parameters and complex behavior. 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?

Given 0 required parameters, 10 params, no annotations, and an existing output schema, the description covers all necessary aspects: param usage, return format, pagination, and examples. No gaps observed.

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 has 0% description coverage, but the description provides detailed 'Args' section with explanations, defaults, and examples for all 10 parameters. Adds significant meaning beyond the schema's property types.

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?

Clearly states it's a unified tool for all instance retrieval patterns, listing specific functions like get by names/IDs, filter by status, search, and list all. Distinguishes itself from sibling tools by consolidating get_instance_details, get_instance_by_name, get_instances_by_status, and search_instances.

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 says to use when user requests instance information, status checks, or searches, but does not provide when-not-to-use or alternative tools beyond the consolidation statement. Sibling list is available externally, but the description itself lacks exclusions.

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