profilarr_get_database

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

Annotations already declare readOnlyHint=true, so the safe-read nature is known. The description adds 'Secrets stripped,' which is a meaningful behavioral disclosure about the response content. This goes beyond the annotation and gives insight into what the tool returns, though no error or rate-limit details are provided.

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 two short, front-loaded sentences: 'Get a single linked database by id. Secrets stripped.' Every word adds value, and the structure is efficiently ordered with the primary action first.

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 simple get-by-id operation with an output schema present, the description adequately covers the core purpose and a key behavioral detail. It does not explain usage alternatives or id provenance, but given the tool's low complexity, this is nearly complete.

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 a single integer 'id' with 0% schema description coverage. The description merely repeats 'by id' without explaining what the id refers to, how to obtain it, or any constraints. It does not compensate for the schema's lack of parameter documentation.

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 a specific verb and resource: 'Get a single linked database by id.' This distinguishes it from sibling tools like list_databases (which gets all) and create/update/delete, and the additional 'Secrets stripped' further specifies the tool's behavior.

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 implies usage when you have a specific id ('by id') and a single database, but it does not explicitly contrast with list_databases or mention when not to use. There is clear context but no exclusions or named alternatives.

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