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

No annotations are provided, so the description carries the full burden. It only says 'Get structured details,' implying a read operation, but does not disclose authentication needs, error handling, response format, or behavior when the listing is absent. This is minimal disclosure for a tool with no annotation support.

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, front-loaded sentence that states the purpose and the parameter source without any filler. Every word contributes to agent understanding.

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 simple read tool with two parameters and an enum, the description covers the main use case and parameter source, but lacks information about the response structure (no output schema) and does not differentiate from request_vendor_contact. Given the absence of annotations and output schema, more context about expected return values would improve completeness.

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 0%, so the description must compensate. It adds value by linking both parameters to the output of search_nc_wedding_directory, telling the agent exactly where to obtain valid values. However, it does not explain the format of slug or the meaning of category beyond the schema's enum.

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 the tool retrieves structured details for a single venue or vendor and references the source of its parameters (search_nc_wedding_directory). This distinguishes it from the sibling search tool (listing) and the contact tool (requesting contact info) by the specific action and 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?

It explicitly instructs the agent to use the category and slug returned by the search tool, establishing a clear prerequisite and workflow. However, it does not explicitly contrast with request_vendor_contact or state when not to use this tool, so no exclusions are given.

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