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

The description asserts 'Read-only, changes nothing', but the annotations declare readOnlyHint: false, so the stated behavioral claim conflicts with the structured safety metadata. The remaining behavioral notes (one receipt per field, fallback to a platform equivalent, 3 MESH cost) are useful but do not resolve the direct read/write contradiction.

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?

A single sprawling em-dash sentence mixes purpose, field list, fallback behavior, a safety claim, and a pricing/ops tag with no front-loading of the core action. Terms like 'front door', 'receipt per field', and 'walk-around' add length without adding precision.

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 an open-world tool with no output schema and a nested, unspecified input object, the description never explains what a caller supplies or gets back beyond an abstract field list. It also fails to clarify the safety profile it muddles with 'Read-only, changes nothing'.

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 description coverage is 100%, so the baseline is 3, but the schema's own text is generic boilerplate ('Capability-specific payload, e.g. agent-brain...') that gives no clue what this specific tool expects. The description could have said whether to pass a place name, URL, or platform handle, and it does not.

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 verb ('Checks') and enumerates the fields it looks at (name, what it is, who it is for, link, location, verified status, public count), so the general purpose is inferable. However, the phrasing 'any place's front door live' is idiosyncratic jargon that never plainly says it fetches an organization/business profile page, and nothing distinguishes it from siblings such as readme-check, listing-upgrade-checker, or pinned-repos-check.

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 when-to-use or when-not-to-use guidance and no named alternative among the many sibling check tools. The only conditional content ('a walk-around to that platform's equivalent if a field is absent') describes internal fallback behavior rather than routing advice for the agent.

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