fitbit_status

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

Annotations already establish this as a safe, non-destructive, closed-world read, so the bar is lower. The description still adds real behavioral context beyond them: the warning that declared support does not guarantee data availability on the device, and an explicit statement that credentials are not returned, which is security-relevant for a connection-status tool.

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?

Three short, front-loaded sentences with no filler; the return content comes first and the caveats follow. Slightly telegraphic phrasing, but every sentence 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?

With no parameters, no output schema, and annotations covering the safety profile, this is a low-complexity diagnostic call and the description covers the essentials: what it returns and the two important caveats. It does not enumerate the returned fields, but that is a minor gap at this complexity level.

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 tool takes zero parameters, so per the baseline the schema carries no parameter burden and the description has nothing to compensate for. No parameter information is needed or missing.

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 names the resource ('local connection metadata and implemented types'), which tells an agent roughly what comes back, but it is a bare noun phrase with no verb and no statement of what the tool actually does. It also does not distinguish itself from near siblings like fitbit_devices or fitbit_operation, so the purpose is only 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?

There is no statement of when to call this versus fitbit_devices, fitbit_operation, or fitbit_read. The caveat 'declared support is not proof of data availability on this device' is a data-quality warning, not usage guidance, and no prerequisites or exclusions are given.

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