MyDankTank Public Information MCP

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description does not need to restate safety. It adds some scoping context ('public', 'authority exclusions') but does not describe response behavior, pagination, rate limits, or what the returned surfaces actually contain. No contradiction with annotations.

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 sentence with no filler and is front-loaded with the verb and target. However, the dense terminology ('machine-discovery surfaces', 'evidence boundaries') could be unpacked without adding significant length.

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 zero input parameters and rich read-only annotations, the description is mostly adequate for invoking the tool. However, with no output schema present, it should more clearly explain what each returned category contains; the current phrasing is high-level and somewhat ambiguous.

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 tool has zero parameters and schema description coverage is 100%, so the baseline of 4 applies. The description rightly does not need to explain parameters, and it does not add any parameter-specific meaning.

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 uses a concrete verb ('Return') and names a specific resource ('MyDankTank public machine-discovery surfaces, evidence boundaries, and explicit authority exclusions'). It is not a tautology and is reasonably distinguishable from siblings like get_public_policies or search_catalog_education, though the noun phrases are jargon-heavy and could be clearer.

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 gives no guidance on when to use this tool versus its siblings. It does not mention alternatives, conditions, prerequisites, or exclusions, so an agent must infer the appropriate context from the name alone.

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

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

The annotations already declare read-only, idempotent, and non-destructive behavior, so the description does not need to repeat that. It adds the useful context that the result set is a fixed 'canonical' collection of public pages, but it does not describe response format or further behavioral details.

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 sentence with the core action and qualification front-loaded. The appended resource list is information-dense and directly useful, with no filler or redundancy.

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 no-parameter, read-only resource listing, the description adequately conveys what the tool returns and which resources are included. It does not specify the exact response format, but the low complexity and strong annotations make that absence non-critical.

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 tool has zero parameters, so there is no parameter semantics for the description to explain; the baseline of 4 applies. The description's list of returned resources is relevant to output, not to 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 uses a specific verb ('Return') and identifies a concrete resource category ('canonical public informational and policy resources') with an explicit list of examples. This clearly distinguishes it from sibling tools like search_journal or search_catalog_education, which are search-oriented.

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 does not explicitly state when to use this tool instead of its siblings, nor does it mention any alternatives or exclusions. The resource list implies a static-information use case, but the agent is left to infer the boundary with search_journal.

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

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds useful context that the taxonomy is public and that no transactional fields are returned, clarifying the output scope without contradicting the annotations.

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 compact sentences with no redundancy. The primary purpose is front-loaded, followed by a single clarifying note about the absence of transactional fields.

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 one-parameter, read-only list tool, the description covers the purpose, the public nature, and the output scope. It lacks explicit output structure and limit-default behavior, but annotations cover safety and the overall complexity is low.

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 0%, and the description gives no information about the 'limit' parameter beyond what the schema min/max already state. It does not explain default behavior, pagination, or how the limit affects results, so the description fails to compensate for the low coverage.

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 uses a specific verb ('List') and specific resource ('public product-category taxonomy'), and explicitly states what is returned ('names and descriptions for machine classification'). It also contrasts with sibling tools by noting 'No transactional fields are returned,' making its scope clear.

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 provides clear context: use this tool to get public taxonomy data for machine classification. The note about no transactional fields helps route away from transactional data tools, but it does not explicitly name alternatives or state when not to use this tool.

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

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

Annotations already establish that the tool is read-only, idempotent, and non-destructive. The description adds meaningful behavioral context by stating that no price, stock, purchase URL, cart, or ordering data is returned, and that only published catalog descriptions are searched. This goes beyond the structured annotations and helps set expectations about the return payload.

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 two sentences with no fluff. The primary purpose is stated immediately, and the second sentence succinctly clarifies the scope exclusions. Every word earns its place, and the structure is front-loaded with the core action.

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 two-parameter search tool with no output schema, the description covers the core purpose and exclusions but leaves important operational details unstated, such as how limit affects results, whether pagination is supported, and what the result format looks like. The lack of an output schema raises the burden on the description to explain return behavior, which it only partially does.

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 input schema has no descriptions (0% coverage), so the description must compensate. It gives some semantic meaning to the query parameter by specifying it searches educational metadata fields, but the limit parameter is entirely undocumented in both the schema and description. No guidance is provided on how limit behaves, default values, or pagination.

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 searches published MyDankTank catalog descriptions for educational metadata, naming specific dimensions (product-format, flavor, lineage, descriptive metadata). It also explicitly excludes commerce data. However, it does not differentiate from sibling tools by name, so some inference is required to distinguish it from search_journal or list_catalog_taxonomy.

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 implies a use case (finding educational catalog metadata) but provides no explicit guidance on when to choose this tool over alternatives like search_journal or list_catalog_taxonomy. There are no when-to-use or when-not-to-use statements, so the agent must infer the appropriate context.

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

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds useful context beyond annotations by restricting results to 'published' content and specifying the return fields, which helps an agent anticipate outcomes. It does not mention pagination or ranking, but this is minor for a simple read-only search.

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 focused sentence that front-loads the action and resource, then lists the return fields. There is no filler or redundant repetition of schema properties.

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 provides the essential purpose and return fields, and annotations cover read-only safety. However, with no output schema and zero parameter explanation, it does not fully inform the agent about query semantics, limit behavior, or edge cases like empty results. It is minimally adequate but has clear gaps.

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 0%, so the description must compensate for parameter semantics. It does not explain how the 'query' string is matched, what 'limit' controls, or what values are acceptable beyond the schema constraints. This leaves the agent without meaningful guidance for the two 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 uses a specific verb ('Search'), identifies a distinct resource ('published MyDankTank Journal/editorial content'), and lists the return payload (titles, excerpts, dates, canonical URLs). This clearly differentiates it from the sibling catalog and policy tools.

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 implies usage by naming the target content type (Journal/editorial), but it does not explicitly say when to prefer this tool over alternatives or when not to use it. Sibling names suggest different content domains, but no direct routing guidance is provided.

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