Get App Store guideline by ID or section number

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

Annotations already declare the read-only, idempotent, non-destructive, non-open-world profile, so the safety burden is lifted. The description adds a genuinely non-obvious behavioral trait: fuzzy prefix-matching when no exact match exists, which tells the agent it may receive a neighboring section rather than a miss.

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?

Two sentences, zero filler. The primary purpose and the accepted inputs lead, and the fallback caveat follows — well front-loaded and appropriately sized for a two-parameter lookup tool.

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?

No output schema exists, so the description carries the return-value burden and does address it ('full text'), plus the format parameter governs markdown vs. json. It doesn't state what happens when neither exact nor prefix matching succeeds, which is the remaining small gap.

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%, so both parameters (id, format) are already documented in the schema, including the slug/number formats and the enum. The description restates the id forms without adding meaning, and says nothing about the format parameter beyond what the enum provides.

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?

States a concrete verb and resource ('Retrieve the full text of a specific App Store Review Guideline section') and enumerates the accepted identifier forms (anchor slug vs. section number). This is clearly distinguishable from the sibling appstore_guidelines_search, which would return matching sections rather than one full section.

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 accepted input forms imply usage ('use this when you know the section id'), but no explicit when-to-use guidance or alternative routing to appstore_guidelines_search is given. The prefix-matching fallback note is behavioral rather than usage guidance, so the tool selection guidance remains implied.

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