bitpull_authorize_folder

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

The only annotation is destructiveHint=false, so the description carries most of the disclosure burden. It does add real value by declaring that this grants read scope specifically and that human confirmation is required first, which annotations do not cover. However it says nothing about persistence, scope of access (recursive or not), or how the grant is later revoked.

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 short sentences, zero filler, with the action stated first and the prerequisite/consent condition trailing it. Every clause carries information an agent needs.

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?

For a one-parameter authorization tool with no output schema, the description covers what it does, when it is needed, and the consent requirement, which is enough to call it correctly. The remaining gap is what happens after authorization (persistence, revocation), which is secondary for the call decision.

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% and the single parameter already documents itself as an absolute folder path, so the schema does the heavy lifting. The phrase "a folder of this computer" reinforces that the path is local rather than remote, but adds no format, validation, or edge-case detail 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?

"Let BitPull read a folder of this computer" states a specific verb (grant read access) and resource (a local folder), and frames it as an authorization step rather than a generic folder operation, which separates it from the remove/add-folder siblings. It stops short of naming those siblings explicitly, so the differentiation is implied rather than stated.

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 gives a concrete ordering cue — "needed before preparing or publishing it" — so an agent knows this is a prerequisite call, and it adds an operating constraint ("Confirm with the person first"). It offers no explicit when-not guidance or mention of the sibling removal/revocation tools.

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