Connection info

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior beyond that: the response is mode-dependent — in demo mode it also returns this session's access log. What's still missing is any hint about what the permission set looks like or how failures behave, but for a zero-parameter read tool this is solid added context.

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 sentences, no filler, with the core capability front-loaded and the conditional demo-mode behavior second. The opening clause is slightly awkwardly phrased as a noun phrase rather than a verb phrase, which is the only structural weakness.

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 output schema and no parameters, the description carries the return-value burden and does reasonably well: it says the result covers permissions, the full-entry-text flag, and demo-mode access log. It could go one step further by noting the shape or that the call always succeeds, but an agent has enough to call it correctly.

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?

There are zero input parameters, so the baseline is 4. The description correctly adds nothing about arguments and instead spends its words on what the response contains, which is the right allocation.

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 a specific resource — the permissions of this Nocturne connection — plus the notable field 'whether full entry text is on', which no sibling tool covers (siblings list entries, songs, timelines, entry text). It lacks an explicit verb, but the noun phrase is unambiguous enough that an agent can tell it apart from list_entries or get_entry_text.

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?

Usage is only implied: an agent can infer this is the tool to call to check capabilities (e.g. whether full entry text is available) before or after fetching content. There is no explicit when-to-use statement, no exclusions, and no mention of alternatives, so the routing guidance is left to inference.

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