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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds value by naming the fields and explaining that doors_elsewhere entries carry a URL and optional platform. However, with no output schema, it does not fully describe the return structure or whether fields can be absent.

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?

It is a single dense sentence with no filler, but the phrase 'where it takes any other kind instead' is grammatically awkward and forces the reader to reparse it. The field list is front-loaded, but the doors_elsewhere clause could be clearer.

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 zero-parameter read with no output schema, the description does list the main return categories and partly explains doors_elsewhere. It still leaves the response shape and the meaning of 'other kind' ambiguous, and gives no usage context. It is minimum viable rather than 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 tool takes zero parameters, so there is nothing for the description to clarify about inputs. The baseline for a no-parameter tool is 4.

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 enumerates the profile fields returned (name, time zone, currency, languages, accepted item types, doors_elsewhere), which makes the resource clear. It never uses an explicit verb like 'returns' or 'retrieves', but the field list leaves little doubt it is a business-profile read. It is distinguishable from all transactional siblings.

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 use this tool versus siblings, and no prerequisites or exclusions. The only implied usage is that an agent needs business configuration, which is left entirely to inference.

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