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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description saying 'Read-only' is redundant. It adds the context 'Works in every server mode' and generic SAP execution guidance about pricing and routing. No contradiction exists with annotations, but the tool-specific behavioral disclosure is minimal and largely restates what annotations already convey.

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 first sentence is concise and front-loaded, but the description includes a large block of generic 'SAP MCP execution guidance' that appears to be boilerplate and is not specific to this tool. This bloats the description and the guidance text does not earn its place in this tool's description, making it poorly structured overall.

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?

The tool is simple with an output schema and annotations covering safety, so the description is adequate. It explains the purpose, read-only nature, and server mode compatibility. However, it lacks explicit differentiation from sibling tools and includes generic boilerplate rather than tool-specific contextual detail, leaving a gap in usage decision-making.

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 both parameters (agent and targetDir). The description adds high-level context about 'local agent skill directories' but does not provide additional meaning or usage details beyond what the parameter descriptions already contain. With full schema coverage, a baseline of 3 is appropriate.

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 a specific action: 'Compare the bundled skill version with the latest published npm package and report which local agent skill directories are stale.' This is a precise verb+resource+scope and is distinct from sibling tools like sap_skills_upgrade_plan or sap_skills_self_update, which focus on performing updates rather than checking them.

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: it is a read-only check for stale skill directories, and it notes 'Works in every server mode.' However, it does not explicitly state when to use this tool versus alternatives (e.g., upgrade plan or self-update), nor does it provide exclusions or alternative tool references. Usage guidance is only implied.

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