sac_get_story_detail

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

Without annotations, description explains the OData endpoint, return behavior (parsed JSON or raw body+content type), and hints at the rawBody/maxRawChars parameters. No explicit statement of being read-only, but it's implied by 'fetch'. Good transparency overall.

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 concise sentences, front-loaded with main purpose. Every word adds value. No fluff.

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?

Given no output schema, description adequately explains what is returned and how parameters affect output. It mentions the OData navigation and when to use, making it complete for a fetch tool.

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 coverage is 100%, baseline 3. Description adds value by explaining the return behavior in context of rawBody and maxRawChars parameters, showing how they affect output. This enhances understanding beyond schema descriptions.

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?

Description clearly states the tool fetches structural pages and widgets of a story via OData navigation. It distinguishes from sibling sac_get_story by specifying when to use this tool for more detail. Verb 'Fetch' is specific and resource is clearly identified.

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?

Explicitly states 'Use this when sac_get_story metadata is not enough' and gives an example (inspect widget definitions or page layouts). This provides clear when-to-use guidance and implies alternative.

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