get_worksheet_protection

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

The annotation readOnlyHint=true already communicates the safe, read-only nature. The description adds no further behavioral context, such as return format, error behavior, or scope constraints. It simply restates the purpose without elaborating on what 'status and option flags' means for the caller.

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, concise sentence with no filler or redundant content. It is front-loaded with the primary action and target. Every word earns its place.

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 lack of an output schema, the description should explain what 'status and option flags' includes or how the return value is structured. Because it does not, the agent lacks critical information about the tool's output. The tool is simple, but the description is still incomplete for making an informed invocation.

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%, with two parameters (filepath, sheet_name) that have no descriptions. The description does not explain or specify these parameters; it only implies that sheet_name refers to the worksheet and filepath to the file. This is minimal compensation and leaves the agent to guess parameter formats or constraints.

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 function: 'Get worksheet protection status and option flags.' It uses a specific verb ('get') and resource ('worksheet protection'), and the purpose distinguishes it from the sibling tool 'set_worksheet_protection', which would be the write counterpart.

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 provides no guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or any relationship to sibling tools such as set_worksheet_protection. The agent is left to infer usage from the tool's name.

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