Circuitry MCP Server

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

With no annotations provided, the description carries full burden but only states the basic operation. It doesn't disclose whether this is a read-only operation, performance characteristics, error conditions, or what happens with empty sheets. 'Get' implies reading, but explicit safety/behavior details are missing.

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?

Single sentence efficiently conveys purpose, resource, and output format with zero wasted words. Front-loaded with the core action ('Get all formulas') followed by essential details.

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 read operation with 100% schema coverage but no annotations or output schema, the description adequately covers the basic purpose. However, it lacks details about return format structure, error handling, or performance considerations that would be helpful for an agent.

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% with the single parameter 'nodeId' well-described as 'Sheet node ID or name'. The description adds no additional parameter context beyond what the schema provides, maintaining the baseline score for high schema 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 clearly states the specific action ('Get all formulas') and resource ('in a Sheet'), with precise output format ('as a map of cell keys to formula strings'). It distinguishes from sibling tools like sheet.getCellFormula (single cell) and spreadsheet.getCellFormula (different resource scope).

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 for retrieving all formulas from a sheet, but provides no explicit guidance on when to use this vs. alternatives like sheet.getCellFormula for single formulas or sheet.getDataPaginated for non-formula data. No prerequisites or exclusions are mentioned.

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