get_instructionsGet the VarynForge agent guide — workflow paths (free vs paid), token-economy rules, walls and upgrade conversation conventions. Read this at session start.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotation readOnlyHint=true already establishes that this call is safe and non-mutating. The description adds useful content-scope context (the guide covers free/paid paths, token economy, walls/upgrade conventions) but does not mention response format, potential delays, or any further behavioral detail. Given the annotation coverage, the description adds moderate but not extensive behavioral transparency.
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 one sentence, front-loaded with the action and resource, followed by a compact content list and a clear usage instruction. Every clause contributes value, with no filler or repetition of the tool name in a tautological way.
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 zero-parameter, read-only instruction-retrieval tool, this description fully covers what the agent needs: what it returns, why it matters, and when to invoke it. The absence of an output schema is not a gap here because the nature of the content is clearly described and the annotation confirms safety.
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 the schema is effectively empty with 100% schema coverage. The baseline for a no-parameter tool is 4, and the description appropriately focuses on the resource and the reason to call it rather than inventing parameter guidance.
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 states a specific verb and resource: 'Get the VarynForge agent guide', and further clarifies what that guide contains (workflow paths, token-economy rules, conventions). This makes it clearly distinguishable in intent from sibling get_* tools like get_onboarding_guide or get_changelog, even though it does not name an alternative 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?
"Read this at session start" provides an explicit, actionable condition for when the tool should be used. It does not list alternatives or exclusions, but the temporal directive is strong and concrete enough for an agent to know this is the first-instruction retrieval step.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have distinct purposes, but a few pairs could confuse an agent: add_article_suggestion vs create_article_suggestion_with_input, and get_article_brief vs download_brief_markdown vs get_write_handoff all deal with brief content. The detailed descriptions help disambiguate, but the overlap is real.
All tool names follow a consistent verb_noun pattern in lowercase snake_case (create_project, list_opportunities, generate_article_brief, lint_draft). There is no mixing of camelCase, acronyms, or vague verbs, making the naming predictable and readable.
50 tools is excessive for an MCP server, even for a broad platform like content operations. While the scope is large, this many tools will overwhelm agents and increase latency and context cost. Most practical servers are well under 25.
The tool surface covers the full content lifecycle: project creation, research, opportunity clustering, content planning, briefs, drafting, linting, publishing, and reporting. Minor gaps exist (e.g., no delete_project, no remove_destination, no direct analytics beyond distributions), but they are workarounds or handled in the web UI.