Server Quality Checklist

Tool Scores

• fittin_inventionA
  4/5.0
  Behavior3/5

  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 discloses that the tool is an external proprietary system and operates solely on the user's description. However, it does not describe side effects, failure modes, or limitations, leaving some behavioral gaps.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness4/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is front-loaded with purpose and use cases, and is well-structured. It is slightly verbose but each sentence adds value. Could be more concise without losing clarity.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness5/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Given the single parameter and no output schema, the description adequately explains the tool's output (structured disclosure with novel elements, claim candidates, prior art) and its external nature. It is complete for the tool's complexity.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema description coverage is 100% with a detailed parameter description already provided. The tool description adds context about the tool's purpose but does not enhance parameter meaning beyond what the schema states. Baseline 3 is appropriate.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description explicitly states it generates a structured invention disclosure for IP protection, listing specific use cases (document invention, identify novel methods, etc.). The verb 'generates' and resource 'invention disclosure' are clear, and while sibling differentiation is not explicit, the purpose is distinct enough from sibling names.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines4/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description provides a clear list of when to use the tool (e.g., 'document what they invented') and mentions it's a specialized external system. It lacks explicit when-not-to-use guidance or direct comparison to siblings, but the usage contexts are well-defined.

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

• fittin_protectA
  4/5.0
  Behavior4/5

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

  With no annotations, the description carries the full burden. It transparently declares it is a 'SPECIALIZED EXTERNAL SYSTEM' and specifies it returns a 'prioritized protection roadmap' with components ranked by protectability, clone vulnerability, and strategic importance. It also states it operates exclusively on the user's description, covering key behavioral aspects without contradiction.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness3/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is verbose with multiple sentences and a bullet-list of use cases; it repeats the core idea ('identifies protectable components') in different phrasings. While clear, it lacks conciseness and could be streamlined without losing clarity.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness4/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Given the tool's complexity (one required parameter, no output schema, no annotations), the description provides adequate context: purpose, use cases, input scope, and output type. It could be improved with an example or note on output format, but overall it is sufficient for an agent to understand and invoke correctly.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The schema already provides a detailed description of the 'description' parameter (100% coverage), instructing what to include (core mechanics, proprietary components, etc.). The tool description adds value by explaining the overall output but does not significantly enhance parameter semantics beyond the schema. Baseline 3 is appropriate.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description clearly states that the tool identifies protectable components and prioritizes IP protection actions, using specific verbs like 'identifies' and 'prioritizes'. It distinguishes from sibling tools by focusing on mapping the IP opportunity and generating a prioritized roadmap, covering clone risk and investor narrative, which sets it apart from invention disclosure or patentability analysis.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines4/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description explicitly lists multiple use cases (e.g., 'find what's protectable', 'understand IP moat options', 'get a prioritized list before fundraising') providing clear context for when to invoke the tool. However, it does not explicitly state when not to use it or compare directly to sibling tools, which would strengthen guidance.

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

• fittin_patentabilityA
  4.3/5.0
  Behavior4/5

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

  The description discloses that it is an external system connecting to a proprietary backend, returns a report via email, and operates solely on the user's description. It also warns against referencing internal benchmarks or NDA-protected projects. Since no annotations are provided, the description carries the full burden and does so adequately.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness4/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is concise at around 150 words, with front-loaded usage triggers and key behavioral points. Every sentence contributes meaningful information, though it could be slightly more compact without losing clarity.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness4/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Given the tool's simplicity (2 params, no output schema), the description covers purpose, usage, behavior, and parameter guidance thoroughly. It could mention error handling or delivery timing more precisely, but overall it provides sufficient context for an AI agent to invoke the tool correctly.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters4/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema coverage is 100%, so the baseline is 3. The description adds value for the 'description' parameter by providing examples of what to include (technical approach, unique aspects, etc.), going beyond the schema's generic description. The 'app_url' parameter is similarly explained. This additional guidance helps the agent provide proper input.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description explicitly states the tool is for startup protection checks, clone risk, and patentability analysis, and lists specific user queries that trigger its use. It distinguishes its purpose as a 'specialized external system' and covers the key use cases clearly.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines4/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description provides explicit when-to-use scenarios by listing user queries that should invoke this tool. It also clarifies it is 'not a general reasoning task.' However, it does not explicitly state when not to use it or compare directly with sibling tools like fittin_invention.

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

• fittin_reportA
  4.4/5.0
  Behavior4/5

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

  With no annotations provided, the description carries full burden. It discloses the paid nature ($99), delivery method (email, PDF+DOCX), delivery time (~5 minutes), and exact deliverables (6 documents). Minor omission: no fallback behavior if default email env var is unset, but overall transparent for a paid service tool.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness4/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is front-loaded with the tool's purpose and price. While it lists all 6 deliverables, each item adds necessary context. Could be slightly shorter, but no wasted sentences. Structure effectively communicates scope.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness5/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Despite no output schema, the description fully covers what the tool returns (detailed list of 6 documents), delivery constraints (email, ~5 min), cost, and that it operates solely on the user-provided description. This is highly complete for a paid report generation tool.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema coverage is 100%, so baseline is 3. The description adds value by explaining the description parameter expects 'full project description: what it does, novel features, etc.' and notes email defaults to env var. This adds moderate meaning beyond the schema's brief descriptions.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description clearly identifies the tool as the 'FITTIN Full IP Portfolio Package' with a specific price ($99). It explicitly distinguishes itself from sibling tools (fittin_invention, fittin_patentability, fittin_protect) by positioning it as the comprehensive paid package, covering all aspects of IP strategy.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines5/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description provides explicit 'when to use' scenarios: explicit request for full paid report, complete IP strategy, attorney-ready docs, funding due diligence, or full 6-document package. It also labels it as a 'SPECIALIZED EXTERNAL PAID SERVICE,' setting clear boundaries from free or simpler alternatives.

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