get_resource

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

No annotations are provided, so the description must disclose behavioral traits. It says 'Get full details' but does not explain what 'full details' includes, whether it's read-only, error handling for invalid identifiers, or any side effects. For a simple lookup, it's adequate but not thorough.

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?

Two sentences: first states what the tool does, second states when to use it. No wasted words; front-loaded with essential information. Excellent conciseness.

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's low complexity (1 parameter, no output schema, no annotations), the description is mostly complete. It covers purpose and usage context. However, it omits any detail about return format or constraints, which prevents a perfect score.

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?

The schema covers the single parameter 'identifier' with a description ('Resource ID or exact title to look up') at 100% coverage. The description adds no new semantic value beyond restating the parameter's role, so baseline 3 applies.

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 clearly states 'Get full details about a specific AI resource' with a specific verb and resource. It indicates lookup by ID or exact name. While it doesn't explicitly differentiate from siblings like search or recommend, the purpose is clearly about retrieving details of a known resource.

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 states 'Use this when the user wants more information about a previously recommended resource,' providing clear context. It could be improved by mentioning when not to use (e.g., if the resource is already fully known or for other operations), but the guidance is direct and helpful.

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