put_netshare_afp

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

The description only indicates an update operation (write) and lists error codes. With no annotations, it fails to disclose other behavioral traits such as idempotency, side effects, or authorization needs.

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?

Extremely concise, but poorly structured. Could include a sentence about purpose and another about usage, but lacks formatting or prioritization of key information.

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?

With 5 optional parameters, an output schema, and no annotations, the description is minimal and incomplete. It does not explain the output, common use cases, or parameter combinations.

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?

Input schema has 5 parameters, all with descriptions (100% coverage). The description adds no additional meaning beyond the schema, so baseline score applies.

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 'Update the AfpConfig' clearly states the action and resource. It effectively distinguishes from sibling 'put_netshare_samba' by name, but does not elaborate on what the AfpConfig encompasses.

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?

No guidance on when to use this tool versus alternatives like put_netshare_samba or related get tools. No context on prerequisites or common usage scenarios.

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