get_guideline

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

With no annotations, the description carries the behavioral burden. It discloses that this fetches live content directly from developer.apple.com and returns Markdown, implying a read-only network operation, but does not mention failure behavior, rate limits, authentication, or invalid-topic handling.

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 front-loaded sentence with no wasted words. The core action, scope, output format, and source are stated immediately.

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 one-parameter fetch tool with no output schema, the description states the source and return format sufficiently. It leaves minor gaps around error handling and topic resolution, but is otherwise complete for invoking the 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?

Schema description coverage is 100%, and the schema already explains the topic parameter with examples. The description restates 'any Apple HIG topic' but adds no additional resolution rules, formats, or constraints 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?

Uses a specific verb and resource: 'Fetch the complete, live Markdown content of any Apple HIG topic directly from developer.apple.com.' It clearly states what is returned and from where, but does not differentiate this tool from siblings such as search_hig or list_topics.

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 use when full topic content is needed, but gives no explicit when-to-use guidance, prerequisites, or alternatives. It does not tell the agent when to use get_guideline versus search_hig or list_topics to discover a topic.

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