list_howto_pagesList every published how-to page on stepcode.dev — 36 analysis x tool cells (Excel, Google Sheets, R, Python, SQL, DAX/Power BI) with slug, title, analysis family, tool, vertical and whether the tool's approach diverges from the others.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| count | Yes | ||
| pages | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish this is a safe read-only operation. The description adds useful behavioral scope: only published pages, all 36 analysis x tool cells, and the divergence flag. It does not mention ordering or pagination, but the fixed small set and zero parameters make those less critical.
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 dense sentence leads with the verb and resource, then packs the scope and returned fields into a well-organized em-dash clause. There is 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?
With no parameters, an output schema available, and annotations covering the safety profile, the description provides the remaining essential context: exactly what the listing contains and its scope. Nothing critical is missing for an agent to invoke this tool correctly.
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 zero parameters and 100% schema description coverage, so there is no parameter burden for the description to carry. No parameter documentation is needed.
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 opens with a specific verb and object: 'List every published how-to page on stepcode.dev.' It then enumerates the exact fields returned, making it clearly distinct from get_howto_page (single page) and search_howto_pages (filtered lookup).
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 clearly implies this is for full enumeration of all how-to pages, but it does not explicitly state when to choose this tool over search_howto_pages or get_howto_page. No alternatives or exclusion conditions are named.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.