sigma_get_doc_page

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds that the return is 'full page content' in Markdown, but does not mention error behavior, rate limits, or other edge cases. This matches the baseline expectation when annotations exist.

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 brief and front-loaded with the main action. The second sentence provides useful examples. The 'read_only_hint: True' line is redundant with annotations, but it does not significantly bloat the description.

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-only fetch tool with one parameter and an output schema, the description is complete. It states what is returned ('full page content') and how to target the page. No additional context is needed given the low complexity.

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 schema's page_slug parameter has no description, and coverage is 0%. The description compensates by explaining it accepts a slug or section path and gives examples ('create-a-workbook', 'docs/create-a-workbook'). This adds meaningful semantic information beyond the schema.

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 ('Fetch'), identifies the resource ('Sigma documentation page'), and specifies the output format ('clean Markdown'). It distinguishes from siblings by focusing on fetching a specific page via slug or path, unlike sigma_search_docs.

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?

Clear guidance is given on what to pass (page slug or section path) with concrete examples. It does not explicitly state when not to use this tool or name alternatives, but the use case is straightforward and well implied.

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