sharing_shares_get

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

The description adds no behavioral details beyond the annotations (readOnlyHint). It does not disclose error handling, authentication requirements, or any side effects. The annotations already indicate that this is a read-only operation, but the description provides no additional transparency.

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 sentence with the endpoint URL, which is concise and front-loaded. Every element adds value without unnecessary verbosity.

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 the input schema fully described and readOnlyHint annotation, the description is minimally complete. However, it lacks usage guidelines and error handling context. The existence of an output schema is mentioned in the context signals, so the description does not need to detail return values.

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?

The input schema has 100% coverage with descriptions for both parameters. The description adds context by showing the endpoint URL structure, which indicates how parameters are used (path vs query). This slightly enhances understanding, but does not add significant new meaning 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?

The description clearly states the action 'Get a Delta Sharing share' with a specific verb and resource. It distinguishes from siblings like sharing_shares_create, sharing_shares_delete, sharing_shares_list, and sharing_shares_update by indicating a retrieval operation.

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 is provided on when to use this tool versus alternatives such as sharing_shares_list or sharing_shares_get. The purpose is implied by the name, but there is no explicit context or conditions for use.

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