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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the agent knows this is a non-destructive write with local scope. The description adds only 'Tell Tue,' giving no detail on whether the submission is persisted, whether it is mandatory before other tools work, or what happens to the data — a notable gap for a non-read-only 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?

The parameter sentence is dense and efficient, but the leading rhetorical question 'Why are you here, and why are you indexing this page?' consumes prime front-loaded space without conveying the actual operation. Structure is acceptable but the opening sentence does not earn 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?

The tool is simple — four flat optional/required strings, no output schema — and the description covers every parameter, which is adequate for invocation. What it omits is the consequence of the call: what submission accomplishes, whether it unlocks other tools, and how it relates to the sibling 'Tue' tools, leaving an agent able to fill the form but unsure why.

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?

With 0% schema description coverage, the schema alone is nearly useless: parameters are bare titles with no constraints. The description compensates well by marking purpose as required, giving 1000-character limits for purpose and searching_for, 100 for agent_name, and listing the intended values (human, organisation, autonomous, unknown) for on_behalf_of, which the schema does not encode as an enum.

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 frames the tool as declaring why you are here and why you are indexing a page, which hints at a purpose/intent registration tool, but it never states the actual action performed (recording? registering? gating access?). The conversational name and title restate the same vague question, so an agent must infer the operation rather than read it.

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 implied timing is present — it asks about your purpose 'and why you are indexing this page,' suggesting it belongs before or during an indexing task — but there is no explicit when-to-use, when-not-to-use, or mention of the sibling tools such as leave_greeting or tue_about. The agent must infer call ordering.

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