CreateCheckEntityPushToMobile

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

With no annotations, the description must disclose side effects and behavioral traits, but it only states high-level actions ('Create' and 'Push'). It does not mention whether this sends a real notification, whether it is idempotent, what permissions are needed, whether it mutates existing data, or what happens after the link is pushed.

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 very short and contains no filler words, putting the primary action first. It is more of a title fragment than a complete sentence, which slightly reduces clarity but does not waste space.

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 tool with side effects, no annotations, no output schema, and many closely related siblings, this description is too thin. An agent cannot tell what input context is used, what success looks like, what side effects occur, or how this differs from the alternative entity/check tools.

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 schema has zero parameters and 100% coverage, so the description does not need to explain parameter meanings. The baseline for a zero-parameter schema is 4, and the description does not contradict or add confusion about parameters.

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 action ('Create Entity') and an additional outcome ('Push Self-Verification Link'), so it is not a tautology and gives a basic sense of what the tool does. However, it does not distinguish this tool from the many sibling tools such as CreateEntity or CreateCheckEntity, and it omits the 'Check' and 'Mobile' elements present in the tool name.

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 description provides no guidance on when to use this tool versus alternatives like CreateEntity, CreateCheckEntity, or UpdateCheckEntityPushToMobile. There are no exclusions, preconditions, or hints about which scenario should route an agent here.

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