sf_skills_get

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It reveals the source repository (forcedotcom/sf-skills), but does not mention external network access, authentication requirements, error behavior, or return format. This is insufficient for a tool without annotation support.

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 a single, focused sentence that directly states the tool's purpose. It is appropriately sized and front-loaded, with no unnecessary words or repetition of schema details.

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 the simple fetch operation, the description provides a baseline understanding, but it is incomplete. It does not explain what includeReferences does or what the tool returns (e.g., raw markdown content, path, etc.), especially since no output schema exists.

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 0%, so the description must compensate. It does not mention either parameter (skillName or includeReferences). While skillName is somewhat inferable from the tool name, includeReferences remains entirely unexplained, leaving ambiguity.

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 clearly states the tool fetches a Salesforce skill definition (SKILL.md) from a specific repository (forcedotcom/sf-skills). The verb 'Fetch' and resource are specific, distinguishing it from sibling tools like sf_skills_search (search) and sf_skills_list_domains (list domains).

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 usage when a specific skill name is known, but it does not explicitly compare with alternatives like sf_skills_search or sf_skills_list_domains. There is no mention of when to use this versus searching, so guidance is only implied by the verb 'Fetch'.

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