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

There are no annotations, so the description carries the full burden of disclosing behavior. 'Self-describing manifest' communicates that the tool is informational and read-only, and 'all endpoints' sets expectations about scope. However, it does not describe what the returned manifest contains, how it is structured, or that no arguments are needed, though the empty schema and output schema mitigate this somewhat.

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 a single concise sentence with no wasted words. It front-loads the core identity of the tool and avoids repeating the name or title.

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 meta-tool with an output schema, the description is mostly complete: it states what the manifest covers and implies a read-only enumeration use case. It could be stronger by explicitly saying 'use this to list all available endpoints,' but the combination of name, description, and empty schema provides sufficient context for an agent 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?

The tool has zero parameters, so the baseline is 4. The description adds context about the tool being a manifest of all endpoints, which is sufficient for a no-argument tool.

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 identifies a specific resource: a self-describing manifest of all OSINT Terminal agent endpoints. The word 'manifest' conveys that the tool returns a catalog of endpoints, even though there is no explicit verb like 'list' or 'get'. It does not clearly distinguish itself from the sibling tool named 'manifest', but for a zero-parameter meta-tool the purpose is reasonably clear.

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 phrase 'all OSINT Terminal agent endpoints' implies this tool should be used to discover or inspect the full endpoint catalog. However, the description gives no explicit when-to-use guidance, no exclusions, and no mention of alternatives such as the sibling 'manifest' tool. The usage is implied rather than stated.

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