Search noble houses from A Song of Ice and Fire and Game of Thrones by name, with result limits, to find house details for lore research or fan projects.
Search noble houses from A Song of Ice and Fire (Game of Thrones).
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | House name to search for | |
| limit | No | Results per page (default 10) |
Changes observed during successful MCP inspections.
v0.1.11Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full disclosure burden. It implies a read-only search but says nothing about pagination behavior (relevant given the limit param), rate limits, authentication, or what happens when no matches are found.
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?
A single tight sentence with the verb, resource, and disambiguating franchise context front-loaded. Nothing is wasted.
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 two-param search tool with a fully documented schema and no output schema, the description is minimally sufficient. It omits pagination/result-shape context that limit would imply, leaving a small gap.
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 description coverage is 100%, so both the name and limit parameters are already documented in the schema (including the default of 10). The description adds no additional parameter meaning, 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?
The description gives a specific verb ("Search") and resource ("noble houses"), plus the franchise context, so the agent knows exactly what it retrieves. It is inherently distinguished from siblings like iceandfire_books and iceandfire_characters by the resource, though it never names them explicitly.
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?
There is no guidance on when to use this tool versus the sibling iceandfire_books or iceandfire_characters, nor any prerequisites or exclusions. The agent must infer usage purely from the resource noun.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.