Tentahead MCP

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

While annotations declare readOnlyHint and non-destructive behavior, the description adds minimal behavioral context beyond listing filters. It does not explain what 'supported parks' means (scope of dataset), does not clarify pagination behavior despite limit/offset parameters being present, and provides no indication of result format or default sorting.

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, compact sentence that efficiently lists the available search dimensions without redundancy. However, given the tool's complexity (8 optional parameters) and lack of output schema, this extreme brevity leaves critical information unstated.

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?

The description covers the primary search intent and filter categories but leaves significant gaps for an 8-parameter tool with no output schema. It omits the optional nature of parameters, pagination instructions, and return value structure. It is minimally viable but incomplete.

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?

With only 25% schema description coverage (only 'near' and 'state' have descriptions), the description compensates well by semantically mapping conceptual filters to parameter names: 'origin'→near, 'drive time'→max_drive_minutes, 'camping types'→has_spot_types, and 'group-camping support'→has_group_camping. It misses documentation for limit/offset pagination parameters.

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 verb (Search), resource (parks), and specific filter dimensions available (origin, drive time, activities, camping types, group-camping). However, it does not differentiate from sibling tools like 'find_campsites' or 'get_park_details', leaving ambiguity about which tool to use for camping-specific queries versus general park discovery.

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?

No guidance is provided on when to use this tool versus alternatives like 'find_campsites' or 'get_park_details'. It also fails to mention that all parameters are optional or what behavior occurs when no filters are applied.

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