Publish SAP Tool By Name

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

Annotations indicate readOnlyHint=false and destructiveHint=false, consistent with publishing. The description adds context about SDK method and registry writes, but doesn't disclose details like overwrite behavior or permission requirements. Still, it adds value beyond annotations.

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 front-load the purpose and context. The second sentence includes examples that are somewhat verbose but relevant. Overall, it is efficient and well-structured.

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 10 parameters, full schema coverage, output schema, and annotations, the description provides sufficient context about the tool's role and when to use it. It could mention authorization or side effects, but it is complete enough for a publish operation.

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%, so the schema already documents all parameters. The description does not add new parameter semantics beyond stating 'publish only schemas and descriptions that match actual tool surface,' which is general guidance. Baseline 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 the tool's purpose: 'Publish a tool descriptor using SDK ToolsModule.publishByName.' It specifies the resource (tool descriptor) and the action (publish), and provides context about advertising capabilities. Examples of tools (e.g., bridging_bridgeWormhole) help differentiate from siblings like sap_update_tool.

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 says to 'use tool registry writes to advertise concrete capabilities,' which guides when to use. It does not explicitly state when not to use or contrast with sap_update_tool, but the context is clear. A small gap in mentioning alternatives prevents a 5.

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